> Only one caveat left. It still creates a copy of the utility xsd's
> classes... They are in their own seperate package (which matches the
> original jar), but they are being re-generated. Is there a way to prevent
> that (since it javadocs/jars the entire subtree)?
While neither an elegant nor long-term solution, with Maven you have the
ability to work around "project silliness" such as that with the preGoal and
postGoal Jelly tags in maven.xml. You can hook the java:build preGoal target
to remove the offending package from the filesystem with an ant:delete and its
ant:fileset friends (if your package is complex enough to warrant their use):
[maven.xml]
preGoal name="java:build"
ant:delete dir="${maven.build.dir}/jaxb/org/eoti/foo/bar" /
Maven forever!
-- /v\atthew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net