www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Sanchez" <car...@apache.org>
Subject Re: Relocation on a different version
Date Wed, 28 Nov 2007 12:19:49 GMT
2.0.2 is relocated to 1.0.b2 means 2.0.2=1.0.b2
after you do the replacement you can resolve that 1.3.03 evicts 1.0.b2
(2.0.2 is like never existed)

my 0.02

On Nov 28, 2007 8:13 PM, Gilles Scokart <gscokart@gmail.com> wrote:
> Yes, I understand that someone decided to rename the version number.
>
> My problem is that I don't know how to consider the version number in the conflict resolution.
 If I consider the
> version number of the relocated module or the version number of the 'target of the relocation',
the result will be
> different.
>
> If I take the example of xml-apis, the version 1.3.03 evict the 1.0.b2, and 2.0.2 is
relocated to 1.0.b2.  Should 2.0.2
> evict 1.3.03 or not?
> Even worse, should 2.0.2 evict 1.0.b2?  If not, that means that eviction can only be
performed after reading both pom.
> In this example the relaction is done toward a smaller version number, but it could be
in the opposite.
> Does the 'b' in this particular case play a role?
>
> I'm lost with it.  I have the feeling that inconsistent things are introduced by the
relocation, but I didn't manage to
> pinpoint what.
>
> BTW, even if this is not very frequent, it is at least used by xml-api, which is himself
very frequently used.
>
> Gilles
>
>
> > -----Original Message-----
> > From: carlossg@gmail.com [mailto:carlossg@gmail.com] On Behalf Of Carlos Sanchez
> > Sent: mercredi 28 novembre 2007 11:40
> > To: repository@apache.org
> > Cc: Maven Developers List
> > Subject: Re: Relocation on a different version
> >
> > that was because it was published under two different versions, so one
> > was relocated to the correct one. Not common though
> >
> > On Nov 28, 2007 6:38 PM, Gilles Scokart <gscokart@gmail.com> wrote:
> > > As there is no answer in the repository list, maybe I will have more chance
on the maven list.
> > Sorry for the
> > > cross-post.
> > >
> > > Is there anyone who can explain why it is allowed to relocate a module to an
other revision
> > number?  And how it is
> > > supposed to work with conflict resolution?
> > >
> > > Thanks,
> > > Gilles
> > >
> > >
> > > > -----Original Message-----
> > > > From: Gilles Scokart
> > > > Sent: vendredi 23 novembre 2007 9:01
> > > > To: 'repository@apache.org'
> > > > Subject: Relocation on a different version
> > > >
> > > >
> > > > Is it allowed to relocate a module to itself by only changing the version
number? This lead to
> > > > scenario very complex to solve when you consider the conflict resolution
(the module is in
> > conflict
> > > > with himself depending how you choose the name).
> > > >
> > > > See [1] for an example of such a case. This example is very annoying because
it is a dependency
> > > > very widely used [2].
> > > >
> > > > [1] ftp://ibiblio.org/pub/packages/maven2/xml-apis/xml-apis/2.0.2/xml-apis-2.0.2.pom
> > > > [2] http://mvnrepository.com/artifact/xml-apis/xml-apis/2.0.2
> > > >
> > > >
> > > > Gilles
> > >
> > >
> >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> >                              -- The Princess Bride
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>



-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

Mime
View raw message