Re: V2.x not usable next to V1.x

Rolf, Thanks for moving this discussion forward.  I trust Gary and Brad can
choose the best option of those you listed.

I'm a fairly naive maven user (that is: it just works for me - once I got
over the starting hurdles - and if it doesn't work I blame m2e and not
maven :-)

Idea: I have used Ivy in order to do some custom publishing from an Ant
build.  I wanted to suggest that Ivy might be more suitable for JDOM's
needs?  Ivy is just a .jar that knows how to speak to Maven.

--Joe

On Fri, May 18, 2012 at 12:12 PM, Rolf Lear wrote:

>
> So, the fix for this problem appears to be putting future versions of jdom
> 2.x in to a separate artifact. If the fix is accomplished by changing the
> artifact ID, then great... the way I see it is:
>
> 1. leave it the way it is and have psycho's on jdom-interest whining ;-)
> 2. put jdom-2.0.2.jar in the jdom artifact, as now, but also deploy
> jdom2-2.0.2.jar to jdom2 artifact (double-release to maven)
> 3. put jdom-2.0.2.jar and future versions in jdom2 artifact (assuming I
> can have a different jar 'base' name than artifact name).
> 4. put jdom2-2.0.2.jar and future versions in jdom2 artifact, and keep the
> 'standard' jdom-2.0.2.jar on jdom.org, but that *sux* to have different
> jars on www.jdom.org and maven-central.
> 5. rename all of JDOM's future jars to jdom2-2.x.y.jar to accomodate the
> maven 'problem' ( ;-) ) and then 'conform' to maven-mantra.
>
>

_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/[email protected]