Hi guys,
Sorry if it was already discussed but do you know what will be the future of 
the groupId? Now that all plugins are moving to GitHub are we still allowed to 
deploy on central with groupId org.codehaus.mojo? AFAIK Maven conventions are 
that we should own the domain codehaus.org to deploy artifacts with groupId 
org.codehaus.*
And if the plan is to change the groupId, this is a big change since 
org.codehaus.mojo is hardcoded into Maven as a "default" groupId. It means for 
example that SonarQube users simply have to run mvn sonar:sonar without any 
special configuration. So I need to know what are the plan in order to prepare 
transition (may need to update documentation, Jenkins plugin, ...).
Thanks
Julien

Reply via email to