Apache Commons NET currently uses the groupId commons-net. However, it should really use the groupId org.apache.commons.
Is it possible to set up the Maven repos so that this change is transparent to users? Or does changing a groupId necessarily involve change for end-users? == AIUI, a redirect pom can be created, which will cause references to commons-net to be seen as org.apache.commons, at least when downloading. For example: NET 2.0 groupId = commons-net Create NET 2.x with groupId org.apache.commons Then a project that references commons-net:commons-net:2.x will download org.apache.commons:commons-net:2.x (though there will be a warning logged) [For example, see JDom 1.1, which changed groupId jdom => org.jdom] However, what happens if a project has (transitive) dependencies on both versions of Net? Does Maven know how to resolve these correctly so that only the 2.x release of Net is used? Or is it necessary to change the Net package name in order to avoid conflict? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
