[ http://jira.codehaus.org/browse/MJAR-27?page=all ]
Mike Perham closed MJAR-27:
---------------------------
Assign To: Mike Perham
Resolution: Fixed
Fix Version: 2.1
Committed the latest version. As biased as I am towards testing, the plugin
does not have a working integration test as is and I think it is asking a bit
much to expect patch submitters to create test infrastructure from scratch for
a 5-10 line 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
> Assignee: Mike Perham
> Fix For: 2.1
> Attachments: MJAR-27-maven-jar-plugin.diff, MJAR-27-maven-jar-plugin.patch,
> 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
