the last revision - 1.0.5, I think - was relicensed CDDL.
We already have an xjc plugin in the sandbox. It seems unmaintained, so
we can probably replace it with this. I'd prefer jaxb1-maven-plugin
(drop the 2, they are all maven2 plugins).
- Brett
Jeff Genender wrote:
Yes...that was with my Apache hat on ;-) Sometimes I get confused.
- Jeff
Wayne Fay wrote:
Well if his plugin simply calls the Sun jars, and does not include
them, then it would be up to the Maven User as to whether or not they
could comply with the Sun license and thus use the Jaxb1 plugin. This
jaxb1 pom would need to include those Sun jars as dependencies and
then it would be up to the user to go download them from Sun directly
and install manually into their local or corporate repo.
So I don't see this as any good reason to keep this plugin off the
Codehaus site etc. ;-)
Wayne
On 4/14/06, Jeff Genender <[EMAIL PROTECTED]> wrote:
Whats the licensing on the Sun jars for 1.0? That may be a slight problem.
I know they changed them to CDDL for 2.0.
Jeff
Kostis Anagnostopoulos wrote:
Hi to all,
I have made a Maven2 plugin for JAXB 1.0 compile based on the JAXB 2.0
plugin, hosted on mojo.codehaus.org.
If there is interest (i.e. requirement for JAXB under 1.4 java), i can
upload the code to mojo.codehaus.org.
Here are the nomenclature i intend to use:
groupId: org.codehaus.mojo
artifactId: jaxb1-maven2-plugin
url: http://mojo.codehaus.org/jaxb1-maven2-plugin/
I can give more details about the plugin if required, feel free to ask
me. Me myself have some question about i.e, the proper artifact id,
and such.
I have not write access to svn repository so i will need direction on
how to accomplish such a task, if desired.
Anagnostopoulos Kostis