Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
Patch here for review: http://issues.apache.org/jira/browse/XBEAN-85 This does not include retrotranslator stuff... though if we wanted to add that it would consist of adding this to top-level pom in project/ build/plugins: 8< org.codehaus.mojo retrotranslator-maven-plugin translate-project jdk14 true >8 Lemme know if you guys are cool with this, and I will apply it... though I'd like to know why the xbean-finder tests are throwing OOME too... as well as why xbean-log4j was included in modules, but missing in src. Cheers, --jason On Mar 21, 2007, at 1:30 AM, James Strachan wrote: +1 On 3/21/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: +1 On 3/21/07, Jason Dillon <[EMAIL PROTECTED]> wrote: > > Looks like xbean-naming is still compiling for 1.4. Is there any > specific reason for this? Can we switch all of xbean to compile for > 1.5... and if you need 1.4 compat, then use the retrotranslator- maven- > plugin's translate-project goal to make jdk14 artifacts? > > --jason > > > On Mar 20, 2007, at 5:14 AM, David Jencks wrote: > > > geronimo-naming jar > > > > I think you'll find you need to update xbean-naming. > > > > thanks > > david jencks > > On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: > > > >> The server/trunk build is picking this up in configs/rmi- naming... > >> but from where? > >> > >> Need to update this to use java.util.concurrent... its using > >> backport-concurrent-util at the moment. > >> > >> --jason > > > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ -- James --- http://radio.weblogs.com/0112098/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
And we are not going to be changing many deps for G 1.2... its almost ready to go... if we leave it alone maybe it will still be ready once AMQ and OpenEJB are ready too ;-) --jason On Mar 21, 2007, at 2:13 PM, David Jencks wrote: On Mar 21, 2007, at 5:07 PM, Guillaume Nodet wrote: Does Geronimo 1.2 uses xbean ? yes, but not 3.0-SNAPSHOT thanks david jencks On 3/21/07, Jason Dillon <[EMAIL PROTECTED]> wrote: Looks like xbean-naming is still compiling for 1.4. Is there any specific reason for this? Can we switch all of xbean to compile for 1.5... and if you need 1.4 compat, then use the retrotranslator- maven- plugin's translate-project goal to make jdk14 artifacts? --jason On Mar 20, 2007, at 5:14 AM, David Jencks wrote: > geronimo-naming jar > > I think you'll find you need to update xbean-naming. > > thanks > david jencks > On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: > >> The server/trunk build is picking this up in configs/rmi- naming... >> but from where? >> >> Need to update this to use java.util.concurrent... its using >> backport-concurrent-util at the moment. >> >> --jason > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
On Mar 21, 2007, at 5:07 PM, Guillaume Nodet wrote: Does Geronimo 1.2 uses xbean ? yes, but not 3.0-SNAPSHOT thanks david jencks On 3/21/07, Jason Dillon <[EMAIL PROTECTED]> wrote: Looks like xbean-naming is still compiling for 1.4. Is there any specific reason for this? Can we switch all of xbean to compile for 1.5... and if you need 1.4 compat, then use the retrotranslator- maven- plugin's translate-project goal to make jdk14 artifacts? --jason On Mar 20, 2007, at 5:14 AM, David Jencks wrote: > geronimo-naming jar > > I think you'll find you need to update xbean-naming. > > thanks > david jencks > On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: > >> The server/trunk build is picking this up in configs/rmi-naming... >> but from where? >> >> Need to update this to use java.util.concurrent... its using >> backport-concurrent-util at the moment. >> >> --jason > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
Does Geronimo 1.2 uses xbean ? On 3/21/07, Jason Dillon <[EMAIL PROTECTED]> wrote: Looks like xbean-naming is still compiling for 1.4. Is there any specific reason for this? Can we switch all of xbean to compile for 1.5... and if you need 1.4 compat, then use the retrotranslator-maven- plugin's translate-project goal to make jdk14 artifacts? --jason On Mar 20, 2007, at 5:14 AM, David Jencks wrote: > geronimo-naming jar > > I think you'll find you need to update xbean-naming. > > thanks > david jencks > On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: > >> The server/trunk build is picking this up in configs/rmi-naming... >> but from where? >> >> Need to update this to use java.util.concurrent... its using >> backport-concurrent-util at the moment. >> >> --jason > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
Yeah, this is what I was thinking too. I'm still -1 but I can easily be outvoted. Regards, Alan On Mar 21, 2007, at 11:46 AM, Jason Dillon wrote: Retrotranslator has been around for a few years AFAIK. Not sure it will double your testing efforts... though if you wanted to run integration tests on JDK 1.5 and 1.4 then ya, it would double those. What additional stuff is there to check for the release? AFAIK the jars contain the same legal bits as non-retro jars. So someone would have to check that once, and then could forget... though there is a goal to ensure artifacts have legal muck in them automatically, which server is using in the default build. Retro jars will live next to non-retro jars with a "jdk14" classifier, everything else should be the same. --jason On Mar 21, 2007, at 11:38 AM, Alan D. Cabrera wrote: Retrotranslator is relatively new and we would only be doubling our testing and it's more stuff to check when we make release distributions. Also, how would our retro jars fit into the maven repository scheme of things? Regards, Alan On Mar 21, 2007, at 10:27 AM, Guillaume Nodet wrote: Why are you both reluctant to publish retrotranslated jars ? On 3/21/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: -1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: > +1 to 1.5 only > +0 to publishing retro-jars > > david jencks > > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: > >> Looks like xbean-naming is still compiling for 1.4. Is there any >> specific reason for this? Can we switch all of xbean to compile >> for 1.5... and if you need 1.4 compat, then use the >> retrotranslator-maven-plugin's translate-project goal to make >> jdk14 artifacts? >> >> --jason >> >> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote: >> >>> geronimo-naming jar >>> >>> I think you'll find you need to update xbean-naming. >>> >>> thanks >>> david jencks >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: >>> The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason >>> >> > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
Should not cause any build problems that I am aware of. If anything does come up I will fix it ;-) Either way... I don't really care... I want JDK 1.5 anyways, 1.4 and retro muck is just for any folks who consume xbean that can't use JDK 1.5. Shall I look into what changes are required? Though I have commit here if you guys wanna see a patch first I can can make one... --jason On Mar 21, 2007, at 11:11 AM, David Jencks wrote: I'm fine (down?) with it as long as it doesn't create build problems and I don't have to set it up. I voted +0, not -0. thanks david jencks On Mar 21, 2007, at 1:47 PM, Jason Dillon wrote: BTW, with the latest retrotranslator-maven-plugin, the translate- project goal makes translation and install/publish transparent, defaulting to using jdk14 for the classifier for the translated bits. I'm also not sure why folks are anti publishing these jars... they are there to support folks who are using JDK 1.4. I suppose if users want they can retrotranslate themselves... but thats more work. Perhaps if folks are still -1 on this, once people start to ask for this they will reconsider? I dunno... seems harmless to retrotranslate them IMO. Not like xbean has 200 modules like G does. --jason On Mar 21, 2007, at 10:27 AM, Guillaume Nodet wrote: Why are you both reluctant to publish retrotranslated jars ? On 3/21/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: -1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: > +1 to 1.5 only > +0 to publishing retro-jars > > david jencks > > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: > >> Looks like xbean-naming is still compiling for 1.4. Is there any >> specific reason for this? Can we switch all of xbean to compile >> for 1.5... and if you need 1.4 compat, then use the >> retrotranslator-maven-plugin's translate-project goal to make >> jdk14 artifacts? >> >> --jason >> >> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote: >> >>> geronimo-naming jar >>> >>> I think you'll find you need to update xbean-naming. >>> >>> thanks >>> david jencks >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: >>> The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason >>> >> > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
Retrotranslator has been around for a few years AFAIK. Not sure it will double your testing efforts... though if you wanted to run integration tests on JDK 1.5 and 1.4 then ya, it would double those. What additional stuff is there to check for the release? AFAIK the jars contain the same legal bits as non-retro jars. So someone would have to check that once, and then could forget... though there is a goal to ensure artifacts have legal muck in them automatically, which server is using in the default build. Retro jars will live next to non-retro jars with a "jdk14" classifier, everything else should be the same. --jason On Mar 21, 2007, at 11:38 AM, Alan D. Cabrera wrote: Retrotranslator is relatively new and we would only be doubling our testing and it's more stuff to check when we make release distributions. Also, how would our retro jars fit into the maven repository scheme of things? Regards, Alan On Mar 21, 2007, at 10:27 AM, Guillaume Nodet wrote: Why are you both reluctant to publish retrotranslated jars ? On 3/21/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: -1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: > +1 to 1.5 only > +0 to publishing retro-jars > > david jencks > > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: > >> Looks like xbean-naming is still compiling for 1.4. Is there any >> specific reason for this? Can we switch all of xbean to compile >> for 1.5... and if you need 1.4 compat, then use the >> retrotranslator-maven-plugin's translate-project goal to make >> jdk14 artifacts? >> >> --jason >> >> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote: >> >>> geronimo-naming jar >>> >>> I think you'll find you need to update xbean-naming. >>> >>> thanks >>> david jencks >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: >>> The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason >>> >> > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
Retrotranslator is relatively new and we would only be doubling our testing and it's more stuff to check when we make release distributions. Also, how would our retro jars fit into the maven repository scheme of things? Regards, Alan On Mar 21, 2007, at 10:27 AM, Guillaume Nodet wrote: Why are you both reluctant to publish retrotranslated jars ? On 3/21/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: -1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: > +1 to 1.5 only > +0 to publishing retro-jars > > david jencks > > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: > >> Looks like xbean-naming is still compiling for 1.4. Is there any >> specific reason for this? Can we switch all of xbean to compile >> for 1.5... and if you need 1.4 compat, then use the >> retrotranslator-maven-plugin's translate-project goal to make >> jdk14 artifacts? >> >> --jason >> >> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote: >> >>> geronimo-naming jar >>> >>> I think you'll find you need to update xbean-naming. >>> >>> thanks >>> david jencks >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: >>> The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason >>> >> > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
I'm fine (down?) with it as long as it doesn't create build problems and I don't have to set it up. I voted +0, not -0. thanks david jencks On Mar 21, 2007, at 1:47 PM, Jason Dillon wrote: BTW, with the latest retrotranslator-maven-plugin, the translate- project goal makes translation and install/publish transparent, defaulting to using jdk14 for the classifier for the translated bits. I'm also not sure why folks are anti publishing these jars... they are there to support folks who are using JDK 1.4. I suppose if users want they can retrotranslate themselves... but thats more work. Perhaps if folks are still -1 on this, once people start to ask for this they will reconsider? I dunno... seems harmless to retrotranslate them IMO. Not like xbean has 200 modules like G does. --jason On Mar 21, 2007, at 10:27 AM, Guillaume Nodet wrote: Why are you both reluctant to publish retrotranslated jars ? On 3/21/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: -1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: > +1 to 1.5 only > +0 to publishing retro-jars > > david jencks > > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: > >> Looks like xbean-naming is still compiling for 1.4. Is there any >> specific reason for this? Can we switch all of xbean to compile >> for 1.5... and if you need 1.4 compat, then use the >> retrotranslator-maven-plugin's translate-project goal to make >> jdk14 artifacts? >> >> --jason >> >> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote: >> >>> geronimo-naming jar >>> >>> I think you'll find you need to update xbean-naming. >>> >>> thanks >>> david jencks >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: >>> The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason >>> >> > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
BTW, with the latest retrotranslator-maven-plugin, the translate- project goal makes translation and install/publish transparent, defaulting to using jdk14 for the classifier for the translated bits. I'm also not sure why folks are anti publishing these jars... they are there to support folks who are using JDK 1.4. I suppose if users want they can retrotranslate themselves... but thats more work. Perhaps if folks are still -1 on this, once people start to ask for this they will reconsider? I dunno... seems harmless to retrotranslate them IMO. Not like xbean has 200 modules like G does. --jason On Mar 21, 2007, at 10:27 AM, Guillaume Nodet wrote: Why are you both reluctant to publish retrotranslated jars ? On 3/21/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: -1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: > +1 to 1.5 only > +0 to publishing retro-jars > > david jencks > > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: > >> Looks like xbean-naming is still compiling for 1.4. Is there any >> specific reason for this? Can we switch all of xbean to compile >> for 1.5... and if you need 1.4 compat, then use the >> retrotranslator-maven-plugin's translate-project goal to make >> jdk14 artifacts? >> >> --jason >> >> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote: >> >>> geronimo-naming jar >>> >>> I think you'll find you need to update xbean-naming. >>> >>> thanks >>> david jencks >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: >>> The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason >>> >> > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
Why are you both reluctant to publish retrotranslated jars ? On 3/21/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: -1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: > +1 to 1.5 only > +0 to publishing retro-jars > > david jencks > > On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: > >> Looks like xbean-naming is still compiling for 1.4. Is there any >> specific reason for this? Can we switch all of xbean to compile >> for 1.5... and if you need 1.4 compat, then use the >> retrotranslator-maven-plugin's translate-project goal to make >> jdk14 artifacts? >> >> --jason >> >> >> On Mar 20, 2007, at 5:14 AM, David Jencks wrote: >> >>> geronimo-naming jar >>> >>> I think you'll find you need to update xbean-naming. >>> >>> thanks >>> david jencks >>> On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: >>> The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason >>> >> > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
-1 (not a veto but a cancelable vote) on publishing retro-jars. Regards, Alan On Mar 21, 2007, at 9:55 AM, David Jencks wrote: +1 to 1.5 only +0 to publishing retro-jars david jencks On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: Looks like xbean-naming is still compiling for 1.4. Is there any specific reason for this? Can we switch all of xbean to compile for 1.5... and if you need 1.4 compat, then use the retrotranslator-maven-plugin's translate-project goal to make jdk14 artifacts? --jason On Mar 20, 2007, at 5:14 AM, David Jencks wrote: geronimo-naming jar I think you'll find you need to update xbean-naming. thanks david jencks On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
+1 to 1.5 only +0 to publishing retro-jars david jencks On Mar 20, 2007, at 11:16 PM, Jason Dillon wrote: Looks like xbean-naming is still compiling for 1.4. Is there any specific reason for this? Can we switch all of xbean to compile for 1.5... and if you need 1.4 compat, then use the retrotranslator- maven-plugin's translate-project goal to make jdk14 artifacts? --jason On Mar 20, 2007, at 5:14 AM, David Jencks wrote: geronimo-naming jar I think you'll find you need to update xbean-naming. thanks david jencks On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
+1 Regards, Alan On Mar 20, 2007, at 8:16 PM, Jason Dillon wrote: Looks like xbean-naming is still compiling for 1.4. Is there any specific reason for this? Can we switch all of xbean to compile for 1.5... and if you need 1.4 compat, then use the retrotranslator- maven-plugin's translate-project goal to make jdk14 artifacts? --jason On Mar 20, 2007, at 5:14 AM, David Jencks wrote: geronimo-naming jar I think you'll find you need to update xbean-naming. thanks david jencks On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: The server/trunk build is picking this up in configs/rmi- naming... but from where? Need to update this to use java.util.concurrent... its using backport-concurrent-util at the moment. --jason
Re: XBean and Java 1.5 (was Re: Where is the src for org.apache.geronimo.gjndi.GlobalContextGBean)
+1 On 3/21/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: +1 On 3/21/07, Jason Dillon <[EMAIL PROTECTED]> wrote: > > Looks like xbean-naming is still compiling for 1.4. Is there any > specific reason for this? Can we switch all of xbean to compile for > 1.5... and if you need 1.4 compat, then use the retrotranslator-maven- > plugin's translate-project goal to make jdk14 artifacts? > > --jason > > > On Mar 20, 2007, at 5:14 AM, David Jencks wrote: > > > geronimo-naming jar > > > > I think you'll find you need to update xbean-naming. > > > > thanks > > david jencks > > On Mar 20, 2007, at 4:03 AM, Jason Dillon wrote: > > > >> The server/trunk build is picking this up in configs/rmi-naming... > >> but from where? > >> > >> Need to update this to use java.util.concurrent... its using > >> backport-concurrent-util at the moment. > >> > >> --jason > > > > -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ -- James --- http://radio.weblogs.com/0112098/
