Skip to main content

Mustang synergy - the sum is less than the total of the parts?

Posted by kirillcool on August 22, 2005 at 11:41 PM PDT

The early access and weekly builds of JAXB 2.0 have been available for quite a few months now right here on java.net. A few weeks ago JAXB 2.0 made its way to Mustang weeklies.

As the minimal JRE requirement for JAXB 2.0 is Tiger (5.0), in case you wish to use it, you have to bundle JAXB 2.0 runtime binaries with your application (unless you are explicitly targeting Mustang). You would expect, of course, to run smoothly under Mustang with the same binaries (even if they provide the same classes). However, that is not the case with the latest build (48) of Mustang - a lot of class-related issues for both design-time (XJC) and runtime binaries of the latest JAXB 2.0 RI weekly. I wouldn't blog here on such a small issue, but it raises more interesting questions.

What is the magnitude and the complexity of taking weeklies from java.net CVS-based projects and putting them to Mustang? Can they be synchronized weekly, or Mustang weeklies are bound to lag behind? Are there some minimal acceptance tests done? How many such java.net projects are integrated weekly (besides JAXB 2.0 and JAX-WS 2.0)? What could be done to ensure that all parts play well when i take the "latest of everything"?

Eventually, i had to remove the Mustang b48 installation completely. Although in command-prompt and IDE i can choose the JRE myself, in Web Start i wasn't able to uncheck the "System" VM (6.0) and make 5.0 to be default. There went another free tester for Mustang - now I'll run all my development under Tiger :(