As far as I know retrotranslator has a maven plugin, so it is just a matter of build process ... I've used it in Ant build process and it was pretty straightforward. The scenario was something like this:
- build the source 1.5 - pack it in a jar - use retrotranslator to make it 1.4 compatible - pack it in a 1.4 jar It was a much simpler project then AMQ but I assume that it should do the trick Regards, Dejan On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
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 > I agree.. but I don't want to condition the switch to 1.5 on getting the retrotranslator stuff working first. If we get the retrotranslator stuff working.. well that should just be the gravy. > 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/ > -- Regards, Hiram Blog: http://hiramchirino.com
