All this emphasizes how important it is to get the GA right in the beginning. As long as no one depends on your artifacts it's not a big deal, but when you have lots of users you will cause issues.
If you absolutely do need to change GA, you must broadcast this to your users very clearly! The issues that could arise are not easily understandable, IMHO, to the normal devs just using Maven as a magic dependency management tool. /Anders On Tue, Jan 18, 2011 at 09:04, Stephen Connolly < [email protected]> wrote: > The closest you will get is to deploy a relocation pom at the old GA > with the new V., e.g. at > > <groupId>org.drools</groupId> > <artifactId>drools-repository</artifactId> > <version>5.2.0</version> > > it's not perfect (i.e. it will only notify people using ranges.... and > only fools use ranges!) and it does not do exactly what you want, but > it will at least give a bit more of a hint. > > I should probably add some goals to v-m-p to help trace relocation > poms and add exclusions for the old locations to the tree > > -Stephen > > On 18 January 2011 07:58, Geoffrey De Smet <[email protected]> > wrote: > > Hi, > > > > We have a pom.xml for the drools guvnor repository jar, with this > > identification: > > > > <groupId>org.drools</groupId> > > <artifactId>drools-repository</artifactId> > > <version>5.1.0</version> > > > > Now, for the next version of that jar, we need to change the > identification > > to: > > > > <groupId>org.drools.guvnor</groupId> > > <artifactId>guvnor-repository</artifactId> > > <version>5.2.0</version> > > > > It's the same code in the jar, but the original identification was wrong > and > > we're fixing that now. > > The problem is, what happens if one of our users has this dependency > tree? > > - foo > > -- foo depends on bar > > --- bar depends on org.drools:drools-repository:5.1.0 > > -- foo depends on org.drools.guvnor:guvnor-repository:5.2.0 > > > > Maven will not detect the dependency conflict between > > - org.drools:drools-repository:5.1.0 > > - org.drools.guvnor:guvnor-repository:5.2.0 > > and it will put both of them in the classpath, instead of just 5.2.0. > > > > Is there any way to tell maven in the 5.2.0 pom.xml, something like this: > > <groupId>org.drools.guvnor</groupId> > > <artifactId>guvnor-repository</artifactId> > > <version>5.2.0</version> > > <legacy-identifications> > > <legacy-identification> > > <groupId>org.drools</groupId> > > <artifactId>drools-repository</artifactId> > > <legacy-identification> > > </legacy-identifications> > > So it does detect the dependency conflict and lets just 5.2.0 survive? > > > > -- > > With kind regards, > > Geoffrey De Smet > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
