You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Michael B?ckling (JIRA)" <ji...@codehaus.org> on 2006/02/07 11:35:47 UTC
[jira] Updated: (MJAR-27) jar:sign doesn't check if project prouces
an artifact
[ http://jira.codehaus.org/browse/MJAR-27?page=all ]
Michael Böckling updated MJAR-27:
---------------------------------
Attachment: MJAR-27-maven-jar-plugin.patch
> 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: MJAR-27-maven-jar-plugin.patch, 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org