[Pljava-dev] Compatibility with Java 1.7 and PostgreSQL 9.2? Is this project still alive?

Hello

I can't find Debian packages of plJava for PostgreSQL 9.2 and found
some unanswered questions regarding the availability for 9.2 on
last years mailing list archives.
So is it currently impossible to build against 9.2? Any plans for
updates?

Apart from that, there seem to be problems with Java 1.7.0 as well,
it seems some abstract classes got more methods:

/srv/home/james/Desktop/pljava-1.4.2/src/java/pljava/org/postgresql/pljava/jdbc/TriggerResultSet.java:22:
error: TriggerResultSet is not abstract and does not override abstract
method getObject(String,Class) in ResultSet public class
TriggerResultSet extends SingleRowResultSet

/srv/home/james/Desktop/pljava-1.4.2/src/java/pljava/org/postgresql/pljava/jdbc/SingleRowReader.java:22:
error: SingleRowReader is not abstract and does not override abstract
method getObject(String,Class) in ResultSet public class
SingleRowReader extends SingleRowResultSet

I can file a more verbose report in your bug tracker if you like but
I'm wondering if this project is still alive as the latest release is
from 2011-09 and the latest on the Wiki "Downloads" page even from
2010...

bye,

-christian-

I have a git hub fork where I've worked through these Java 1.6 issues.

https://github.com/Hellblazer/pljava

This is a Maven 3 project, and requires 1.6. Just cd to the top level directory and do:

mvn clean install

Sent from my Tricorder

On Jan 10, 2013, at 2:27 PM, Christian Hammers <ch at lathspell.de> wrote:

> Hello
>
> I can't find Debian packages of plJava for PostgreSQL 9.2 and found
> some unanswered questions regarding the availability for 9.2 on
> last years mailing list archives.
> So is it currently impossible to build against 9.2? Any plans for
> updates?
>
> Apart from that, there seem to be problems with Java 1.7.0 as well,
> it seems some abstract classes got more methods:
>
> /srv/home/james/Desktop/pljava-1.4.2/src/java/pljava/org/postgresql/pljava/jdbc/TriggerResultSet.java:22:
> error: TriggerResultSet is not abstract and does not override abstract
> method getObject(String,Class) in ResultSet public class
> TriggerResultSet extends SingleRowResultSet
>
> /srv/home/james/Desktop/pljava-1.4.2/src/java/pljava/org/postgresql/pljava/jdbc/SingleRowReader.java:22:
> error: SingleRowReader is not abstract and does not override abstract
> method getObject(String,Class) in ResultSet public class
> SingleRowReader extends SingleRowResultSet
>
> I can file a more verbose report in your bug tracker if you like but
> I'm wondering if this project is still alive as the latest release is
> from 2011-09 and the latest on the Wiki "Downloads" page even from
> 2010...
>
> bye,
>
> -christian-
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev at pgfoundry.org
> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130110/f9982e20/attachment.html>

On 01/11/2013 06:27 AM, Christian Hammers wrote:
> Hello
>
> I can't find Debian packages of plJava for PostgreSQL 9.2 and found
> some unanswered questions regarding the availability for 9.2 on
> last years mailing list archives.
> So is it currently impossible to build against 9.2? Any plans for
> updates?
Building against 9.2 works fine for me. Java 1.7 won't work, though.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Sweet. I'm much in favor of moving the code to GitHub. Personally, I
wouldn't mind at all if we base the official code on this fork rather
than the CVS stuff that it origins from (with possible merge if more
things has been added to CVS of course). Ideally, we should have a fork
under "postgres/pljava".

- thomas

On 2013-01-11 01:48, Hal Hildebrand wrote:
> I have a git hub fork where I've worked through these Java 1.6 issues.
>
> https://github.com/Hellblazer/pljava
>
> This is a Maven 3 project, and requires 1.6. Just cd to the top level
> directory and do:
>
> mvn clean install
>
>
> Sent from my Tricorder
>
> On Jan 10, 2013, at 2:27 PM, Christian Hammers <ch at lathspell.de
> <mailto:ch at lathspell.de>> wrote:
>
>> Hello
>>
>> I can't find Debian packages of plJava for PostgreSQL 9.2 and found
>> some unanswered questions regarding the availability for 9.2 on
>> last years mailing list archives.
>> So is it currently impossible to build against 9.2? Any plans for
>> updates?
>>
>> Apart from that, there seem to be problems with Java 1.7.0 as well,
>> it seems some abstract classes got more methods:
>>
>> /srv/home/james/Desktop/pljava-1.4.2/src/java/pljava/org/postgresql/pljava/jdbc/TriggerResultSet.java:22:
>> error: TriggerResultSet is not abstract and does not override abstract
>> method getObject(String,Class) in ResultSet public class
>> TriggerResultSet extends SingleRowResultSet
>>
>> /srv/home/james/Desktop/pljava-1.4.2/src/java/pljava/org/postgresql/pljava/jdbc/SingleRowReader.java:22:
>> error: SingleRowReader is not abstract and does not override abstract
>> method getObject(String,Class) in ResultSet public class
>> SingleRowReader extends SingleRowResultSet
>>
>> I can file a more verbose report in your bug tracker if you like but
>> I'm wondering if this project is still alive as the latest release is
>> from 2011-09 and the latest on the Wiki "Downloads" page even from
>> 2010...
>>
>> bye,
>>
>> -christian-
>> _______________________________________________
>> Pljava-dev mailing list
>> Pljava-dev at pgfoundry.org <mailto:Pljava-dev at pgfoundry.org>
>> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev
>
>
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev at pgfoundry.org
> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130111/617e1f63/attachment.html>

An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130111/b90b0baf/attachment-0001.html>

I took the liberty of forking the Hellblazer/pljava into pljava/pljava.

- thomas

On 2013-01-11 08:22, Thomas Hallgren wrote:
> Sweet. I'm much in favor of moving the code to GitHub. Personally, I
> wouldn't mind at all if we base the official code on this fork rather
> than the CVS stuff that it origins from (with possible merge if more
> things has been added to CVS of course). Ideally, we should have a
> fork under "postgres/pljava".
>
> - thomas
>
> On 2013-01-11 01:48, Hal Hildebrand wrote:
>> I have a git hub fork where I've worked through these Java 1.6 issues.
>>
>> https://github.com/Hellblazer/pljava
>>
>> This is a Maven 3 project, and requires 1.6. Just cd to the top
>> level directory and do:
>>
>> mvn clean install
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130111/7b2a4575/attachment.html>

On 01/11/2013 06:39 PM, Thomas Hallgren wrote:
> On 2013-01-11 01:48, Hal Hildebrand wrote:
>>> I have a git hub fork where I've worked through these Java 1.6 issues.
>>>
>>> https://github.com/Hellblazer/pljava
I'm a bit worried by the changelog on that. The changes to make failures
silent, in particular, are not something I am at all comfortable with,
especially as they appear to be a workaround for an ORM or other
intermediary. If they're going to be there, surely they should be
conditional? "notsupportederror={log|throw|ignore}" ?

The sources and build look like they would benefit from a clean-up, so
that seems like a good idea - but what's this change going to do to
Windows build support?

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130111/26738785/attachment.html>

On 2013-01-11 13:38, Craig Ringer wrote:
> On 01/11/2013 06:39 PM, Thomas Hallgren wrote:
>> On 2013-01-11 01:48, Hal Hildebrand wrote:
>>>> I have a git hub fork where I've worked through these Java 1.6 issues.
>>>>
>>>> https://github.com/Hellblazer/pljava
> I'm a bit worried by the changelog on that. The changes to make
> failures silent, in particular, are not something I am at all
> comfortable with, especially as they appear to be a workaround for an
> ORM or other intermediary. If they're going to be there, surely they
> should be conditional? "notsupportederror={log|throw|ignore}" ?
>
Looking closer at the changes, I wasn't too thrilled about that part
either. Making it conditional seems to be a very good idea.

> The sources and build look like they would benefit from a clean-up, so
> that seems like a good idea - but what's this change going to do to
> Windows build support?
>
Seems some work remain to the the native parts building. Perhaps we
could establish a decent process around this at GitHub? I.e. we use
pljava/pjlava as the base where we enter issues and submit
pull-requests? I'm not at all against adding collaborators to the actual
project either if that would speed up reviews and acceptance of
contributions. Anyone who wants to help, please raise a hand.

Regards,
Thomas Hallgren

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130111/5d99aab6/attachment.html>

Yes, there are some changes that might not be desirable. Always a good idea to read the change log :).

As to the issues, my thought was to make this a flag so the USOE could be conditionally thrown, defaulting to thrown.

Hadn't worked on the C code yet, bit that was on my plate.

In general, I certainly didn't intend for this to replace the current work. I just threw this out because I solved the generic signature issues and have verified that the code works.

Glad people found it useful and I look forward to seeing more work on the fork.

Sent from my Tricorder

On Jan 11, 2013, at 5:50 AM, Thomas Hallgren <thomas at tada.se> wrote:

> On 2013-01-11 13:38, Craig Ringer wrote:
>> On 01/11/2013 06:39 PM, Thomas Hallgren wrote:
>>> On 2013-01-11 01:48, Hal Hildebrand wrote:
>>>>> I have a git hub fork where I've worked through these Java 1.6 issues.
>>>>>
>>>>> https://github.com/Hellblazer/pljava
>> I'm a bit worried by the changelog on that. The changes to make failures silent, in particular, are not something I am at all comfortable with, especially as they appear to be a workaround for an ORM or other intermediary. If they're going to be there, surely they should be conditional? "notsupportederror={log|throw|ignore}" ?
> Looking closer at the changes, I wasn't too thrilled about that part either. Making it conditional seems to be a very good idea.
>
>> The sources and build look like they would benefit from a clean-up, so that seems like a good idea - but what's this change going to do to Windows build support?
> Seems some work remain to the the native parts building. Perhaps we could establish a decent process around this at GitHub? I.e. we use pljava/pjlava as the base where we enter issues and submit pull-requests? I'm not at all against adding collaborators to the actual project either if that would speed up reviews and acceptance of contributions. Anyone who wants to help, please raise a hand.
>
> Regards,
> Thomas Hallgren
>
> _______________________________________________
> Pljava-dev mailing list
> Pljava-dev at pgfoundry.org
> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130111/a2980db6/attachment.html>

Hi,

I decided to create a 'tada' organization instead. That way, we can
manage teams and members of the project etc. Open source organizations
are free at GitHub. So the new location for the pljava project will be
tada/pljava.

Unless I'm missing something, all version CVS history was stripped off
when Hal created his repository? If that's the case, then I'm planning
to recreate the repository from scratch there so that all CVS version
history is retained and then reapply the commits that was made by Hal.

I hope this is OK with everyone.

Thomas Hallgren

On 2013-01-11 17:55, Hal Hildebrand wrote:
> Yes, there are some changes that might not be desirable. Always a good
> idea to read the change log :).
>
> As to the issues, my thought was to make this a flag so the USOE could
> be conditionally thrown, defaulting to thrown.
>
> Hadn't worked on the C code yet, bit that was on my plate.
>
> In general, I certainly didn't intend for this to replace the current
> work. I just threw this out because I solved the generic signature
> issues and have verified that the code works.
>
> Glad people found it useful and I look forward to seeing more work on
> the fork.
>
> Sent from my Tricorder
>
> On Jan 11, 2013, at 5:50 AM, Thomas Hallgren <thomas at tada.se
> <mailto:thomas at tada.se>> wrote:
>
>> On 2013-01-11 13:38, Craig Ringer wrote:
>>> On 01/11/2013 06:39 PM, Thomas Hallgren wrote:
>>>> On 2013-01-11 01:48, Hal Hildebrand wrote:
>>>>>> I have a git hub fork where I've worked through these Java 1.6
>>>>>> issues.
>>>>>>
>>>>>> https://github.com/Hellblazer/pljava
>>> I'm a bit worried by the changelog on that. The changes to make
>>> failures silent, in particular, are not something I am at all
>>> comfortable with, especially as they appear to be a workaround for
>>> an ORM or other intermediary. If they're going to be there, surely
>>> they should be conditional? "notsupportederror={log|throw|ignore}" ?
>>>
>> Looking closer at the changes, I wasn't too thrilled about that part
>> either. Making it conditional seems to be a very good idea.
>>
>>> The sources and build look like they would benefit from a clean-up,
>>> so that seems like a good idea - but what's this change going to do
>>> to Windows build support?
>>>
>> Seems some work remain to the the native parts building. Perhaps we
>> could establish a decent process around this at GitHub? I.e. we use
>> pljava/pjlava as the base where we enter issues and submit
>> pull-requests? I'm not at all against adding collaborators to the
>> actual project either if that would speed up reviews and acceptance
>> of contributions. Anyone who wants to help, please raise a hand.
>>
>> Regards,
>> Thomas Hallgren
>>
>> _______________________________________________
>> Pljava-dev mailing list
>> Pljava-dev at pgfoundry.org <mailto:Pljava-dev at pgfoundry.org>
>> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130112/5e302f9e/attachment.html>

Sounds good to me.

Sent from my Tricorder

On Jan 12, 2013, at 2:16 AM, Thomas Hallgren <thomas at tada.se> wrote:

> Hi,
>
> I decided to create a 'tada' organization instead. That way, we can manage teams and members of the project etc. Open source organizations are free at GitHub. So the new location for the pljava project will be tada/pljava.
>
> Unless I'm missing something, all version CVS history was stripped off when Hal created his repository? If that's the case, then I'm planning to recreate the repository from scratch there so that all CVS version history is retained and then reapply the commits that was made by Hal.
>
> I hope this is OK with everyone.
>
> Thomas Hallgren
>
>
> On 2013-01-11 17:55, Hal Hildebrand wrote:
>> Yes, there are some changes that might not be desirable. Always a good idea to read the change log :).
>>
>> As to the issues, my thought was to make this a flag so the USOE could be conditionally thrown, defaulting to thrown.
>>
>> Hadn't worked on the C code yet, bit that was on my plate.
>>
>> In general, I certainly didn't intend for this to replace the current work. I just threw this out because I solved the generic signature issues and have verified that the code works.
>>
>> Glad people found it useful and I look forward to seeing more work on the fork.
>>
>> Sent from my Tricorder
>>
>> On Jan 11, 2013, at 5:50 AM, Thomas Hallgren <thomas at tada.se> wrote:
>>
>>> On 2013-01-11 13:38, Craig Ringer wrote:
>>>> On 01/11/2013 06:39 PM, Thomas Hallgren wrote:
>>>>> On 2013-01-11 01:48, Hal Hildebrand wrote:
>>>>>>> I have a git hub fork where I've worked through these Java 1.6 issues.
>>>>>>>
>>>>>>> https://github.com/Hellblazer/pljava
>>>> I'm a bit worried by the changelog on that. The changes to make failures silent, in particular, are not something I am at all comfortable with, especially as they appear to be a workaround for an ORM or other intermediary. If they're going to be there, surely they should be conditional? "notsupportederror={log|throw|ignore}" ?
>>> Looking closer at the changes, I wasn't too thrilled about that part either. Making it conditional seems to be a very good idea.
>>>
>>>> The sources and build look like they would benefit from a clean-up, so that seems like a good idea - but what's this change going to do to Windows build support?
>>> Seems some work remain to the the native parts building. Perhaps we could establish a decent process around this at GitHub? I.e. we use pljava/pjlava as the base where we enter issues and submit pull-requests? I'm not at all against adding collaborators to the actual project either if that would speed up reviews and acceptance of contributions. Anyone who wants to help, please raise a hand.
>>>
>>> Regards,
>>> Thomas Hallgren
>>> _______________________________________________
>>> Pljava-dev mailing list
>>> Pljava-dev at pgfoundry.org
>>> http://lists.pgfoundry.org/mailman/listinfo/pljava-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20130112/27f0f31a/attachment.html>