On 4/15/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote: > On Sat, 15 Apr 2006, Brett Porter wrote: > > > 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). > > The '1' indicates JAXB 1.0, not Maven 1. There's also a JAXB 2.0 plugin > (jaxb2-maven-plugin). > > The 1 could be dropped, though, but for other reasons :) > > Btw, isn't there a way to merge the jaxb1 and 2 plugins? Isn't JAXB2 > backwards compatible? i.e. specify jaxb:version="1.0" in the xsd.
Well, it is not that simple to merge. I'll try to give a rough description of JAXB libs: JAXB 1 & 2 are 2 separate open sourced projects hosted in https://jaxb.dev.java.net/. JAXB 2 was desined for java 1.5 (using annotations) and is not (either compile or runtime) backwards compatible. JAXB2 includes a compatible JAXB1 runtime API for code compiled with JAXB1. The XJC 2 initially could produce both JAXB 1 & 2 compatible code (controlled by the use of the version xsd attribute and/or a '-source' option). Later releases of JAXB 2 dropped this feature and suggest to use JAXB 1 directly. So specifying "jaxb:version="1.0" in the xsd is not enough, since one has to specify also the actual version of the JAXB libs to use (for compile and later, for runtime). My belief is that 2 plugins are easier for the JAXB users to grasp, as they are already accustomed to this 1-2 usage pattern. I also believe that these missunderstandings would occure to any candidate user of these plugins, so i suggested a name that leaves no room for mis-interpretations: jaxb1-maven2-plugin ankostis > > If they're not compatible, you could still read that version attribute > and then issue one or the other compiler. > > -- Kenney > > > > > - 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 > > > > > > > -- > Kenney Westerhof > http://www.neonics.com > GPG public key: http://www.gods.nl/~forge/kenneyw.key >
