jar:sign doesn't check if project prouces an artifact
-----------------------------------------------------
Key: MJAR-27
URL: http://jira.codehaus.org/browse/MJAR-27
Project: Maven 2.x Jar Plugin
Type: Bug
Environment: Maven 2.0.2
Latest Jar checkout
Reporter: Michael Böckling
Attachments: jarsign-patch.txt
jar:sign does not skip projects that don't produce an artifact (=pom packaging).
Attached patch to detect this situation and handle it gracefully.
Since similar issues showed up in the Javadoc and Cobertura plugin, too, I was
wondering if an additional mojo annotation like @requireLanguage (project must
have e.e. java as its language) or @requireArtifact (don't execute if this
project does not create an artifact, e.g. has pom packaging) would make sense.
Stuff like this makes it much harder to establish a company-wide standardized
build process, since there are always pom projects in the inheritance
hierarchy...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
