Michael McCandless created MNG-5266:
---------------------------------------
Summary: Can Maven detect package namespace conflicts across
different artifactIds?
Key: MNG-5266
URL: https://jira.codehaus.org/browse/MNG-5266
Project: Maven 2 & 3
Issue Type: Improvement
Components: Artifacts and Repositories
Reporter: Michael McCandless
Priority: Minor
Disclaimer: I know very little about Maven so this could easily be a
silly idea...
Recently, there was a situation where the Apache Lucene/Solr project
had a dependency on the unreleased Apache commons-csv, but in
releasing to Maven, we created the solr-commons-csv artifact, which
then caused problems...
The situation is now resolved (the dependency will be masqueraded in
the next Solr release, by moving the commons-csv sources under a
private package namespace).
But then I thought: could/should Maven, upon publishing, somehow
detect that there was a package namespace conflict across different
artifactIds? This could have caught the problem earlier and saved a
lot of hassle.
Just an idea...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
