Re: maven artifact 3 use case - relocations

2008-03-10 Thread Brett Porter
On 11/03/2008, at 5:31 AM, Brian E. Fox wrote: It seems to me that we need to process all the relocations and normalize an artifact across the spectrum BEFORE we start selecting versions from those ranges. This would need to happen across the graph in case there are conflicts somewhere

maven artifact 3 use case - relocations

2008-03-10 Thread Brian E. Fox
e puts a range on d[1.0,3.0) we would currently stop at 1.2 because that's the last d, but really e2.0 and e3.0 should be considered the same. It seems to me that we need to process all the relocations and normalize an artifact across the spectrum BEFORE we start selecting versions from those ra

Re: Relocations for existing artifacts in the repo

2007-03-18 Thread Carlos Sanchez
n you upgraded a dependency, because if you don't touch your pom (unless you use snapshots) everything would be fine. Upgrading a dependency can have this kind of consequences, bringing dependencies to your build that you don't want. Maybe it'd be good idea to hold relocations until majo

Re: Relocations for existing artifacts in the repo

2007-03-18 Thread Fabrizio Giustina
uot;won't fix" and this makes the problem even harder to solve for users. fabrizio tough one ;) -- Kenney Fabrizio Giustina wrote: > Hi, > I would like to start a discussion on how relocations in the central > repo should be handled. > > I recently noticed more and more a

Re: Relocations for existing artifacts in the repo

2007-03-17 Thread Kenney Westerhof
he downside is that this breaks old builds, but they probably all have fixed versions anyway. Adding a parameter/argument/sysprop to override this would at least let people be aware that there can be unexpected results. tough one ;) -- Kenney Fabrizio Giustina wrote: Hi, I would like to sta

Relocations for existing artifacts in the repo

2007-03-17 Thread Fabrizio Giustina
Hi, I would like to start a discussion on how relocations in the central repo should be handled. I recently noticed more and more artifacts partially relocated in the repo in case of a new upload. With *partially* relocated I means the case of a new version of an existing artifact uploaded with

Re: Relocations

2007-01-13 Thread Carlos Sanchez
On 1/13/07, Brett Porter <[EMAIL PROTECTED]> wrote: Yeah, that was by me. No idea how it ever worked though, it should be in , right? right On 13/01/2007, at 6:33 PM, Jason van Zyl wrote: > Hi, > > Just doing some work on the integration tests and trying to > automate the installation of th

Re: Relocations

2007-01-13 Thread Brett Porter
Yeah, that was by me. No idea how it ever worked though, it should be in , right? On 13/01/2007, at 6:33 PM, Jason van Zyl wrote: Hi, Just doing some work on the integration tests and trying to automate the installation of the support artifacts and I found this: http://svn.apache.org/rep

Relocations

2007-01-12 Thread Jason van Zyl
Hi, Just doing some work on the integration tests and trying to automate the installation of the support artifacts and I found this: http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/ core-integration-testing-support/1.1-old-location/pom.xml Which has a relocation elemen