On 7 December 2010 10:14, Asmann, Roland <[email protected]> wrote:
> Hi all, > > I was wondering if anybody ever had this problem... > > I have a customer who is running a machine with a SUN JDK and one with > an IBM JDK. Now, we've noticed there are some differences between the > two, so I thought it would be best to release their artefacts for both > JDKs... Question is, can I do this somehow with Maven in a single > release-cycle or do I need to make separate releases? > > I would consider running the tests twice and have just one set of artifacts... Otherwise you will have a nightmare of a dependency management. Run the tests first with ibm and second with sun/oracle that way you know your artifacts work on both JREs > Also, they currently have a problem in that they need SUN JDK 6 for most > project, where one single module MUST be built with SUN JDK 5 because of > a change in some classes. They are currently running the compiler-plugin > with a bootclasspath for JDK 5, which isn't beautiful but works. Is > there a way to have a single module use a different JDK from the others? > Have a look at toolchains. Google is your friend. Toolchains support has been available for a while now, I know because I helped get it into a number of plugins. Another thing you might consider is using animal-sniffer-maven-plu...@mojothat way you can verify that the JRE signatures you use are only public signatures and not internal classes that are not part of the published JRE API > > Thanks, > > -- > Roland Asmann > Senior Software Engineer > > adesso Austria GmbH > Floridotower 26. Stock T +43 1 2198790-27 > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 > A-1210 Wien M +43 664 88657566 > E [email protected] > W www.adesso.at > > ------------------------------------------------------------- > >>> business. people. technology. <<< > ------------------------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
