Another issue to keep in mind is that even if you are using JDK6, you will probably someday need to override one of the JARs already in the JDK6 with a newer version to fix some bug. So make sure your solution is flexible enough to handle these types of scenarios.
Glen Am Freitag, den 04.01.2008, 13:15 -0500 schrieb Daniel Kulp: > Out of curiosity, why does having that stuff in the manifest cause a > problem? The classloaders should, by default, grab the stuff from > jre/lib first anyway. Thus, the stuff in the manifest should be > ignored. > > Dan > > > On Friday 04 January 2008, Jeff Zhang wrote: > > Hi, > > > > I work on CXF jdk6 support. My proposal is split > > cxf-manifest-incubator.jar into 2 manifest jars, one includes all > > javax jars embedded in JDK6, such as jaxws, jaxb, stax, jws, > > annotation, etc..., we can call it cxf-specs-manifest.jar. And another > > one contains the rest jars. > > > > If users use JDK5, they include both manifest jars in classpath, if > > use JDK6, they can only include one manifest. For samples shipped with > > CXF, we can define rule in common_build.xml, it get JDK version from > > OS environment, and put right manifest jar into classpath. > > > > Do you think it reasonable? > > > > Thanks > > Jeff > > >
