www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Demers <bdem...@sonatype.com>
Subject Re: Nexus and groupId relocation
Date Thu, 10 Mar 2011 15:27:39 GMT
At the moment we do not have plans to automate this.  People very
rarely do this and they can just manipulate the files on disk if
needed.


On Thu, Mar 10, 2011 at 9:53 AM, sebb <sebbaz@gmail.com> wrote:
> On 10 March 2011 14:44, Brian Demers <bdemers@sonatype.com> wrote:
>> There is no automated support, you would just upload the pom manually.
>
> Any plans to support the process as described in:
>
> http://maven.apache.org/guides/mini/guide-relocation.html
>
> Of course it would not apply to Maven Central (see below).
>
>> Other projects are being moved to:  org.apache.commons:commons-*
>>
>> If you run into any problems with your relocation pom, let me know
>
> I've just been told that Maven Central does not allow existing
> releases to be replaced by relocation poms, so any Commons components
> that want to change groupId will also have to change package name.
>
> This makes relocation unnecessary - and in fact relocation cannot be
> used in such a case, because the artifacts are not replacements.
>
>>
>> On Wed, Mar 9, 2011 at 6:43 PM, sebb <sebbaz@gmail.com> wrote:
>>> Does Nexus offer any support for groupId relocation?
>>>
>>> For example, if Commons decided to relocate
>>> commons-daemon:commons-daemon to org.apache.commons:commons-daemon,
>>> could this be achieved with Nexus?
>>>
>>> Is there a best practice for how to go about setting up the jars with
>>> the new groupIds and creating the relocation POMs for all the old
>>> versions?
>>>
>>
>

Mime
View raw message