Re: [mojo-dev] Jaxb Maven Plugin and Jaxb re-packaging

2014-11-20 Thread Anders Hammar
As long as we agree that the Codehaus svn repo is the canonical repo you could do anything you want. /Anders On Thu, Nov 20, 2014 at 11:39 AM, Lennart Jörelid wrote: > ... and, of course, when package migration and major refactoring is done > we will re-integrate the changes into the Codehaus S

Re: [mojo-dev] Jaxb Maven Plugin and Jaxb re-packaging

2014-11-20 Thread Lennart Jörelid
... and, of course, when package migration and major refactoring is done we will re-integrate the changes into the Codehaus SVN. This may perhaps have been completely evident (or implied); just mentioning it in the interest of clarity. 2014-11-20 11:36 GMT+01:00 Lennart Jörelid : > Considering t

Re: [mojo-dev] Jaxb Maven Plugin and Jaxb re-packaging

2014-11-20 Thread Lennart Jörelid
Considering that this development effort will presumably be somewhat bigger than between common releases, I have made a SVN to GIT conversion to enable branched development in GIT (without creating clutter and confusion in the Codehaus SVN repository). The development GIT repo is found on https://

Re: [mojo-dev] Jaxb Maven Plugin and Jaxb re-packaging

2014-11-20 Thread Anders Hammar
> Oh - and the reason we should use the glassfish JARs is found in the POMs > of the com.sun JAXB jar artifacts, claiming that they are "Old JAXB > ". An example is found below. The corresponding POMs of the > org.glassfish JARs do not claim to be the Old JAXB ... but rather the jaxb > dist

Re: [mojo-dev] Jaxb Maven Plugin and Jaxb re-packaging

2014-11-18 Thread Lennart Jörelid
Oh - and the reason we should use the glassfish JARs is found in the POMs of the com.sun JAXB jar artifacts, claiming that they are "Old JAXB ". An example is found below. The corresponding POMs of the org.glassfish JARs do not claim to be the Old JAXB ... but rather the jaxb distribution.

Re: [mojo-dev] Jaxb Maven Plugin and Jaxb re-packaging

2014-11-18 Thread Lennart Jörelid
Hello there, Duh! I meant version 2.2.11, of course; just a typo on my part. However, in the 2.2.11 JAXB bom you will find the following: 1.7.7 ... which is the root of my question. I cant find an artifact corresponding to the JAXB BOM's dependency on the stax-ex version 1.7.7 in repo1. Am I m

Re: [mojo-dev] Jaxb Maven Plugin and Jaxb re-packaging

2014-11-18 Thread Anders Hammar
> > >1. The org.glassfish.jaxb:jaxb-runtime:2.2.12 depends on the artifact >org.jvnet.staxex:stax-ex:1.7.7 which I can't find in repo1. (Version 1.7.6 >is present, though). I can test refactoring the plugin using the 1.7.6 >version, but I would rather that the normal dependency set