this question was raised in commons when they thought about changing
their groupIds ot org.apache.commons
http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg90223.html
Let's clarify one thing, when you say your build broke due to a
relocation, you mean your build broke when you upgrad
On 3/17/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
I don't understand the second option: if you stop relocating
(not done by maven, but by the pom deployers, right?) when a version exists,
that means you can never relocate. It's no use to
relocate unreleased poms since they won't be present
Hi,
well, this is indeed a problem..
I don't understand the second option: if you stop relocating
(not done by maven, but by the pom deployers, right?) when a version exists,
that means you can never relocate. It's no use to
relocate unreleased poms since they won't be present in the repository
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 a
