From: Jody G. <jga...@re...> - 2008-05-30 17:17:55
|
Martin Desruisseaux wrote: > Jody Garnett a écrit : >> Martin I would like to like to get the library graduated before >> starting to restructure - there is only a limited amount of volunteer >> effort at the moment. We are all booked up on OSGeo graduation; and >> the GeoServer code Sprint, and uDig 1.1 testing... > Yes I was expecting that it would be too short in time... But does the > workaround for Eclipse IDE proposed by Adrian could work for David? As committed Graham Davis can now work and run trunk from both maven and eclipse. gt-metadata The "problem" is fixed in the medium term ... if you are running Java 5 official jaxb 2.1.5 dependencies will be added with scope priority to gt-metadata. Since this is your module; can you please review the change I made to your pom.xml :-) xsd/gt-core Justin is upset (with good reason) that I patched one of his classes to make this happen. Justin is planning on removing his dependency on jaxb completely. > With current configuration (new dependency in metadata toward the real > JAXB library), JAXB is now required for runtime. The "dummy-jaxb" > module was designed for erasing the annotations from the JAR, but the > real JAXB library of course keep those annotations, leading no > NoClassDefFoundError at if JAXB is not presents at runtime. I think I added the jaxb dependency as "provided" - can you confirm? That would mean they are not required for runtime correct... > This is not a big deal for me, since we use JAXB anyway. But I suspect > that other users will dislike. So the question could be formulated > that way: how long David and Justin can live with workaround until we > go ahead with a project re-organisation? We are out of the woods; the work around will hold; with jaxb as a "provided" dependency is the dummy jar still needed? Jody |