Re: Java 5 in Jackrabbit 2.0?
+1 Regards Felix Jukka Zitting schrieb: > Hi, > > Picking up a topic from last summer... > > On Wed, Jun 25, 2008 at 2:36 PM, Jukka Zitting > wrote: >> On Wed, Jun 25, 2008 at 3:14 PM, Stefan Guggisberg >> wrote: >>> i'd be ok with moving to java 5 if we get agreement in the jcr 283 eg >>> to raise the system requirements as well. >> I'll bring the issue up with the expert group. Basically, I see four options: >> >> 1) JSR 283 specifies Java 5 as the platform for JCR 2.0 >> 2) JSR 283 allows the reference implementation to be Java 5 -based >> even if the spec and the TCK are based on Java 1.4 >> 3) We use Java 1.4 up to the point when the JSR 283 RI is branched, >> and upgrade to Java 5 for the Jackrabbit 2.0 release (i.e. we wouldn't >> use many Java 5 features in 2.0, but would open the door for more Java >> 5 stuff in other 2.x releases) >> 4) We stick with Java 1.4 for now >> >> My personal preference would be option 2 or 3, depending on what the >> JSR 283 EG thinks. > > There were no big passions about this in the EG, but it seems clear > that the JSR 283 spec itself will still use Java 1.4 as the base > platform. > > I would propose that we go with option 2, i.e. make Jackrabbit 2.0 > require Java 5. This will give us a number of nice language features, > many new standard library features (most notably > java.util.concurrent), and avoids problems with dependencies that > already require Java 5. Also, Sun's Java 1.4 reached End Of Service > Life status three months ago (after a two-year transition period), so > there is a strong case for not needing support the platform anymore. > > BR, > > Jukka Zitting >
Re: Java 5 in Jackrabbit 2.0?
Jukka Zitting wrote: > I would propose that we go with option 2, i.e. make Jackrabbit 2.0 > require Java 5. +1 Regards, Alex -- Alexander Klimetschek [email protected]
Re: Java 5 in Jackrabbit 2.0?
> I would propose that we go with option 2, i.e. make Jackrabbit 2.0 > require Java 5. +1 make Jackrabbit 2.0 require Java 5. The default jar files could be compiled with "-target 1.5", but we could test and document how to use Retroweaver ( http://retroweaver.sourceforge.net/ ) to convert it to 1.4. I didn't use Retroweaver so far, so I don't know how complicated that would be, and what are the exact restrictions. Regards, Thomas
Re: Java 5 in Jackrabbit 2.0?
Jukka Zitting wrote: > I would propose that we go with option 2, i.e. make Jackrabbit 2.0 > require Java 5. +1 I don't see a reason why we have to wait for the specification to require Java 5. the API wouldn't benefit from that move anyway, unless it gets heavily restructured. regards marcel
Re: Java 5 in Jackrabbit 2.0?
Hi, Picking up a topic from last summer... On Wed, Jun 25, 2008 at 2:36 PM, Jukka Zitting wrote: > On Wed, Jun 25, 2008 at 3:14 PM, Stefan Guggisberg > wrote: >> i'd be ok with moving to java 5 if we get agreement in the jcr 283 eg >> to raise the system requirements as well. > > I'll bring the issue up with the expert group. Basically, I see four options: > > 1) JSR 283 specifies Java 5 as the platform for JCR 2.0 > 2) JSR 283 allows the reference implementation to be Java 5 -based > even if the spec and the TCK are based on Java 1.4 > 3) We use Java 1.4 up to the point when the JSR 283 RI is branched, > and upgrade to Java 5 for the Jackrabbit 2.0 release (i.e. we wouldn't > use many Java 5 features in 2.0, but would open the door for more Java > 5 stuff in other 2.x releases) > 4) We stick with Java 1.4 for now > > My personal preference would be option 2 or 3, depending on what the > JSR 283 EG thinks. There were no big passions about this in the EG, but it seems clear that the JSR 283 spec itself will still use Java 1.4 as the base platform. I would propose that we go with option 2, i.e. make Jackrabbit 2.0 require Java 5. This will give us a number of nice language features, many new standard library features (most notably java.util.concurrent), and avoids problems with dependencies that already require Java 5. Also, Sun's Java 1.4 reached End Of Service Life status three months ago (after a two-year transition period), so there is a strong case for not needing support the platform anymore. BR, Jukka Zitting
Re: Java 5 in Jackrabbit 2.0?
Jukka Zitting wrote: Hi, Sun's Java 1.4.x is reaching EOL status in October, so I was wondering if there's still need for us to continue using Java 1.4 as the baseline for Jackrabbit. Upgrading the minimum platform requirement to Java 5 would give us a) some nice language features, b) the chance to drop the concurrent library dependency, and c) the chance to directly use libraries like Apache Tika that are based on Java 5. Are there good reasons for sticking with Java 1.4? IMHO a natural upgrade point to Java 5 would be Jackrabbit 2.0. +1 Michael BR, Jukka Zitting -- Michael Wechner Wyona - Open Source Content Management - Yanel, Yulup http://www.wyona.com [EMAIL PROTECTED], [EMAIL PROTECTED] +41 44 272 91 61
Re: Java 5 in Jackrabbit 2.0?
On Wed, Jun 25, 2008 at 2:46 PM, Julian Reschke <[EMAIL PROTECTED]> wrote: > Stefan Guggisberg wrote: >> >> jsr 283 currently requires java 1.4 or higher. if jackrabbit 2.0 (i.e. > > Yes. > >> the JCR 2.0 RI) would require java 5 we have a compatibility >> issue. > > Really? Why. Or does the RI need to prove that it can be implemented in Jave > 1.4? no, but the RI should IMO be usable in a wide range of environments supporting JCR. > >> i'd be ok with moving to java 5 if we get agreement in the jcr 283 eg >> to raise the system requirements as well. > > I always wanted that, but I recall people were against it. > > Now that JCR 2.0 does not *use* any Jave 5 features I would argue for > deferring it to a future spec. > > BR, Julian >
Re: Java 5 in Jackrabbit 2.0?
Hi, On Wed, Jun 25, 2008 at 3:14 PM, Stefan Guggisberg <[EMAIL PROTECTED]> wrote: > i'd be ok with moving to java 5 if we get agreement in the jcr 283 eg > to raise the system requirements as well. I'll bring the issue up with the expert group. Basically, I see four options: 1) JSR 283 specifies Java 5 as the platform for JCR 2.0 2) JSR 283 allows the reference implementation to be Java 5 -based even if the spec and the TCK are based on Java 1.4 3) We use Java 1.4 up to the point when the JSR 283 RI is branched, and upgrade to Java 5 for the Jackrabbit 2.0 release (i.e. we wouldn't use many Java 5 features in 2.0, but would open the door for more Java 5 stuff in other 2.x releases) 4) We stick with Java 1.4 for now My personal preference would be option 2 or 3, depending on what the JSR 283 EG thinks. BR, Jukka Zitting
Re: Java 5 in Jackrabbit 2.0?
On Wed, Jun 25, 2008 at 6:21 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Are there good reasons for sticking with Java 1.4? IMHO a natural > upgrade point to Java 5 would be Jackrabbit 2.0. +1 but only if it is in-line with JSR-283 (ie. does not require the reference implementation to actually be compatible with 1.4) Alex -- Alexander Klimetschek [EMAIL PROTECTED]
Re: Java 5 in Jackrabbit 2.0?
Stefan Guggisberg wrote: jsr 283 currently requires java 1.4 or higher. if jackrabbit 2.0 (i.e. Yes. the JCR 2.0 RI) would require java 5 we have a compatibility issue. Really? Why. Or does the RI need to prove that it can be implemented in Jave 1.4? i'd be ok with moving to java 5 if we get agreement in the jcr 283 eg to raise the system requirements as well. I always wanted that, but I recall people were against it. Now that JCR 2.0 does not *use* any Jave 5 features I would argue for deferring it to a future spec. BR, Julian
Re: Java 5 in Jackrabbit 2.0?
On Wed, Jun 25, 2008 at 12:21 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Hi, > > Sun's Java 1.4.x is reaching EOL status in October, so I was wondering > if there's still need for us to continue using Java 1.4 as the > baseline for Jackrabbit. Upgrading the minimum platform requirement to > Java 5 would give us a) some nice language features, b) the chance to > drop the concurrent library dependency, and c) the chance to directly > use libraries like Apache Tika that are based on Java 5. > > Are there good reasons for sticking with Java 1.4? IMHO a natural > upgrade point to Java 5 would be Jackrabbit 2.0. while i agree that moving to java 5 would bring a couple of benefits i am not sure what that would mean WRT to JCR 2.0 and the RI. jsr 283 currently requires java 1.4 or higher. if jackrabbit 2.0 (i.e. the JCR 2.0 RI) would require java 5 we have a compatibility issue. i'd be ok with moving to java 5 if we get agreement in the jcr 283 eg to raise the system requirements as well. cheers stefan > > BR, > > Jukka Zitting >
Re: Java 5 in Jackrabbit 2.0?
Jukka Zitting wrote: Hi, Sun's Java 1.4.x is reaching EOL status in October, so I was wondering if there's still need for us to continue using Java 1.4 as the baseline for Jackrabbit. Upgrading the minimum platform requirement to Java 5 would give us a) some nice language features, b) the chance to drop the concurrent library dependency, and c) the chance to directly use libraries like Apache Tika that are based on Java 5. Are there good reasons for sticking with Java 1.4? IMHO a natural upgrade point to Java 5 would be Jackrabbit 2.0. +1. BR, Julian
Re: Java 5 in Jackrabbit 2.0?
Thomas Müller wrote: Hi, I am for using Java 1.5. +1 for me. Another option would be to switch to Java 1.5 and provide some documentation or a build profile that uses Retroweaver if Java 1.4 is still required. I have never used it and I don't have an opinion on it, just to list the option: http://retroweaver.sourceforge.net/ We've used retroweaver on ESOE (http://esoeproject.org) quite successfully and it is quite a complex code base including lots of JAXB generated stuff. Didn't really have any troubles with it and works well for the clients. Bradley Regards, Thomas On Wed, Jun 25, 2008 at 12:21 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote: Hi, Sun's Java 1.4.x is reaching EOL status in October, so I was wondering if there's still need for us to continue using Java 1.4 as the baseline for Jackrabbit. Upgrading the minimum platform requirement to Java 5 would give us a) some nice language features, b) the chance to drop the concurrent library dependency, and c) the chance to directly use libraries like Apache Tika that are based on Java 5. Are there good reasons for sticking with Java 1.4? IMHO a natural upgrade point to Java 5 would be Jackrabbit 2.0. BR, Jukka Zitting
Re: Java 5 in Jackrabbit 2.0?
Hi, I am for using Java 1.5. Another option would be to switch to Java 1.5 and provide some documentation or a build profile that uses Retroweaver if Java 1.4 is still required. I have never used it and I don't have an opinion on it, just to list the option: http://retroweaver.sourceforge.net/ Regards, Thomas On Wed, Jun 25, 2008 at 12:21 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Hi, > > Sun's Java 1.4.x is reaching EOL status in October, so I was wondering > if there's still need for us to continue using Java 1.4 as the > baseline for Jackrabbit. Upgrading the minimum platform requirement to > Java 5 would give us a) some nice language features, b) the chance to > drop the concurrent library dependency, and c) the chance to directly > use libraries like Apache Tika that are based on Java 5. > > Are there good reasons for sticking with Java 1.4? IMHO a natural > upgrade point to Java 5 would be Jackrabbit 2.0. > > BR, > > Jukka Zitting >
