[jdom-interest] V2.x not usable next to V1.x
garydgregory at gmail.com
Fri May 18 05:29:28 PDT 2012
For good or bad, I ended learning more than I care about Maven being the
release manager for several Apache Commons components.
Our rule in Commons is that when you change a package name, you must change
the Maven artifact id.
My suggestion is to do this in your POM:
Depending on your philosophy, you could also re-publish the Maven artifacts
for 2.0.1. But this is usually considered bad form because the POM needs to
change and you would then have 2 2.0.1 version with different pom.xml in
your sources jar.
On Fri, May 18, 2012 at 6:55 AM, Rolf Lear <jdom at tuis.net> wrote:
> Hi Gary.
> I am not a Maven expert.... and there is not a huge amount of Maven
> *owner* expertise on this list (we have a number of maven *users*, but not
> many people who 'publish'). I have learned enough to 'publish' to maven,
> but I do not even *use* it.
> As such, our maven 'support' may be broken.
> But.... this is a limitation of maven.... not the way we deploy it.
> Can you show us how we should do it differently?
> For your information though, have you seen these sorts of questions.... ?
> On 17/05/2012 11:21 PM, Gary Gregory wrote:
>> Hello JDOM,
>> I cannot use both v2 and v1 in the same Maven or Ivy project because
>> both use the same id in Maven repositories like Maven Central.
>> I want to use v2 in my app but 3rd party jars I use depends on v1.
>> To control your jdom-interest membership:
>> youraddr at yourhost.com<http://email@example.com>
E-Mail: garydgregory at gmail.com | ggregory at apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jdom-interest