Re: Switching to ActiveMQ 4.2 to Java 5???
Well it looks like we have pretty good consensus on moving to java 5 I'll start updating the build shortly. On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: Hi folks, How do you guys feel about switching the minimum run time requirement for ActiveMQ 4.2 to be Java 5?? I'm itching to do this since Java 5 has a much better set of concurrent implementation. We can keep the 4.1.x branch alive as the Java 1.4 compatible version. Also I have a feeling that once we switch to Java 5, someone will figure out how to use retrotranslator to make our Java 5 binaries also run on Java 1.4. But I doubt anybody will make any efforts to look into that until we actually jump to Java 5. So what do you say? Shall we switch ?? -- Regards, Hiram Blog: http://hiramchirino.com -- Regards, Hiram Blog: http://hiramchirino.com
Re: Switching to ActiveMQ 4.2 to Java 5???
On Nov 16, 2006, at 1:55 AM, Endre Stølsvik wrote: Don't be too afraid of changing major-versions - other companies routinely go much further than "one-uping": from 1.4 to 5.0 (:-)), and 2.6 to 7 (Solaris), and 3.11 to 95, 4.0 to 2000, 2000 to 'XP' (!), 4 to 6 (Netscape) and so on!! ;-) Tomcat peculiarly went from 5.0 to 5.5 on its java 1.4->1.5 dependency change (which I believe they somewhat regret - that story is rather difficult to get across without "eh, say again?!"s). AMQ has been good so far about major numbers meaning incompatible wire format changes. I think this is a good idea, and a good thing to remain consistent on. -Brian
Re: Switching to ActiveMQ 4.2 to Java 5???
On Nov 15, 2006, at 9:10 AM, James Strachan wrote: We should switch to Java 5 for compilation and for the default release (since the concurrent stuff is faster & more bug free on Java 5) but maybe provide a retrotranslator version of the jars for those who can't move JVM. i.e. build on Java 5 only - but allow deployments on 1.4 +1 Regards, Alan
Re: Switching to ActiveMQ 4.2 to Java 5???
+1 about time. :) Hiram Chirino wrote: Hi folks, How do you guys feel about switching the minimum run time requirement for ActiveMQ 4.2 to be Java 5?? I'm itching to do this since Java 5 has a much better set of concurrent implementation. We can keep the 4.1.x branch alive as the Java 1.4 compatible version. Also I have a feeling that once we switch to Java 5, someone will figure out how to use retrotranslator to make our Java 5 binaries also run on Java 1.4. But I doubt anybody will make any efforts to look into that until we actually jump to Java 5. So what do you say? Shall we switch ??
Re: Switching to ActiveMQ 4.2 to Java 5???
+1 for 1.5, but perhaps keep the client-side 1.4 compatible? On 11/15/06, James Strachan <[EMAIL PROTECTED]> wrote: +1. We should switch to Java 5 for compilation and for the default release (since the concurrent stuff is faster & more bug free on Java 5) but maybe provide a retrotranslator version of the jars for those who can't move JVM. i.e. build on Java 5 only - but allow deployments on 1.4 On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > Hi folks, > > How do you guys feel about switching the minimum run time requirement > for ActiveMQ 4.2 to be Java 5?? I'm itching to do this since Java 5 > has a much better set of concurrent implementation. > > We can keep the 4.1.x branch alive as the Java 1.4 compatible version. > Also I have a feeling that once we switch to Java 5, someone will > figure out how to use retrotranslator to make our Java 5 binaries also > run on Java 1.4. But I doubt anybody will make any efforts to look > into that until we actually jump to Java 5. > > So what do you say? Shall we switch ?? > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > -- James --- http://radio.weblogs.com/0112098/
Re: Switching to ActiveMQ 4.2 to Java 5???
Hiram Chirino wrote:
On 11/15/06, Endre Stølsvik <[EMAIL PROTECTED]> wrote:
Hiram Chirino wrote:
> Hi folks,
>
> How do you guys feel about switching the minimum run time requirement
> for ActiveMQ 4.2 to be Java 5?? I'm itching to do this since Java 5
> has a much better set of concurrent implementation.
>
> We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
> Also I have a feeling that once we switch to Java 5, someone will
> figure out how to use retrotranslator to make our Java 5 binaries also
> run on Java 1.4. But I doubt anybody will make any efforts to look
> into that until we actually jump to Java 5.
>
Rather big move for a minor version - why not call it ActiveMQ 5 instead
(It'll even align!).
lol.. good point. But I'd hate to have big increases without big
functionality changes especially if the clients are still compatible
with the 4.x stuff.
It is a rather big _requirement_ change, though?
(And you'll probably introduce some internal changes, and you'll remove
a large pile of code (the down-port of concurrent), and .. so on.. going
from Java 1.4 to 1.5.)
IMHO, the story "ActiveMQ 5 only works on java 1.5 ("5"), while ActiveMQ
4 is the older version that works on java 1.4 (and java 1.5)" would be
rather simple to tell, as opposed to exchanging those two versions with
"4.2" and "4.1".
Particularly since I'll bet that you'll have a rather long maintenance
story going with the "java 1.4" branch afterwards - so this won't be a
small nice little "dot-change", as such.
Don't be too afraid of changing major-versions - other companies
routinely go much further than "one-uping": from 1.4 to 5.0 (:-)), and
2.6 to 7 (Solaris), and 3.11 to 95, 4.0 to 2000, 2000 to 'XP' (!), 4 to
6 (Netscape) and so on!! ;-)
Tomcat peculiarly went from 5.0 to 5.5 on its java 1.4->1.5
dependency change (which I believe they somewhat regret - that story is
rather difficult to get across without "eh, say again?!"s).
Then keep ActiveMQ 4.x on 1.4.
Regards,
Endre.
Re: Switching to ActiveMQ 4.2 to Java 5???
about time :) - +1 On 15 Nov 2006, at 16:48, Hiram Chirino wrote: Hi folks, How do you guys feel about switching the minimum run time requirement for ActiveMQ 4.2 to be Java 5?? I'm itching to do this since Java 5 has a much better set of concurrent implementation. We can keep the 4.1.x branch alive as the Java 1.4 compatible version. Also I have a feeling that once we switch to Java 5, someone will figure out how to use retrotranslator to make our Java 5 binaries also run on Java 1.4. But I doubt anybody will make any efforts to look into that until we actually jump to Java 5. So what do you say? Shall we switch ?? -- Regards, Hiram Blog: http://hiramchirino.com
Re: Switching to ActiveMQ 4.2 to Java 5???
On Nov 15, 2006, at 9:10 AM, James Strachan wrote: +1. We should switch to Java 5 for compilation and for the default release (since the concurrent stuff is faster & more bug free on Java 5) but maybe provide a retrotranslator version of the jars for those who can't move JVM. i.e. build on Java 5 only - but allow deployments on 1.4 +1 --jason
