You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Desruisseaux (JIRA)" <ji...@codehaus.org> on 2012/02/15 20:45:03 UTC
[jira] (MNG-5246) Allow inside element
Martin Desruisseaux created MNG-5246:
----------------------------------------
Summary: Allow <classifier> inside <plugin> element
Key: MNG-5246
URL: https://jira.codehaus.org/browse/MNG-5246
Project: Maven 2 & 3
Issue Type: Improvement
Components: Plugins and Lifecycle
Affects Versions: 3.0.4
Environment: All
Reporter: Martin Desruisseaux
Priority: Minor
In the current Maven project descriptor (http://maven.apache.org/ref/3.0.4/maven-model/maven.html), plugins are declared inside {{<build>}} elements by specifying the {{<groupId>}}, {{<artifactId>}} and {{<version>}} elements. However the {{<classifier>}} element is currently not legal for a plugin. I would like {{<classifier>}} to be legal for plugins, like any other dependencies.
*Use case:* I maintain two branches for my project: a development branch on JDK7, and a branch ported to JDK6. I use custom Maven plugins for my build process. However the JDK7 doclet API seems to have some incompatible changes compared to the JDK6 doclet API. In addition some APT (Annotation Processing Tools) API are being removed from JDK8, since they are now merged with the javac API. For various reasons (may also be reasons specific to my projects), I wish slightly different Maven plugins depending if I'm building my JDK6 branch or my JDK7 branch. I would like to simply use my custom Maven plugins with the same classifier than the project I'm building, but this is currently not possible.
--
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