Re: Sharing common groupId

From a permissions point of view for deployment to the Central Repository via repository.apache.org or OSSRH from Sonatype there is no problem setting this up. The concept used in the Nexus Repository Manager is called repository target and works via pattern matching the path into the Maven repo. That is typically groupId but can also go down to the artifactId level.

And btw. when organized well the concept of a shared groupId for plugins for very well. In fact Maven itself uses it (org.apache.maven.plugins) and mojohaus does to. Other projects like jenkins do it as well. 

There is the added need to manage the artifactId names but that is imho not to bad and it give the plugins under that groupId a more official status than others as a distinction. You could tie this to some sort of quality status...

Manfred

sebb wrote on 2016-11-16 04:00:

> On 16 November 2016 at 10:10, Lukasz Lenart <[email protected]> wrote:
>> Hi,
>>
>> I would like to know if there is any problem if multiple different
>> projects shares the same groupId? I meant, we would like to allow
>> third parties to use common groupId as mentioned in the post below
>>
>> http://markmail.org/message/yruabvlfpfdfw6w5
>>
>> Can this be a problem during publishing artifacts?
> 
> Yes. It can cause severe problems.
> 
> Maven uses the (groupId,artifactId) pair to determine which jars can
> appear on the same classpath.
> 
> Unless all the projects sharing the groupId ensure that they use
> distinct artifact Ids this can result in jar hell.
> 
> The simplest way to ensure distinct (groupId,artifactId) pairs is to
> ensure each independent project uses different groupIds.
> They can then maintain their own unique list of artifactIds.
> 
> A simple analogy: should we allow other organisations to use hostnames
> under the apache.org domain?
> That _could_ be made to work, but - just don't go there.
> 
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>