Dennis Lundberg wrote:
I'm looking into http://jira.codehaus.org/browse/MSHARED-131 which triggered the question in the subject. Maven Archiver and Maven WAR Plugin, and I'm guessing the Dependency Plugin as well, treats a non-existing classifier (classifier == null) differently to an empty classifier (classifier == ""). [...] What is the correct way to handle this?
Looking at DefaultArtifact.hasClassifier() and its caller DefaultArtifact.getDependencyConflictId() and DefaultRepositoryLayout.pathOf(), I think null and the empty string need to be treated the same for consistency with existing core behavior.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
