[ https://jira.codehaus.org/browse/MJAR-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MJAR-27: ------------------------------- Summary: jar:sign doesn't check if project produces an artifact (was: jar:sign doesn't check if project prouces an artifact) > jar:sign doesn't check if project produces an artifact > ------------------------------------------------------ > > Key: MJAR-27 > URL: https://jira.codehaus.org/browse/MJAR-27 > Project: Maven JAR Plugin > Issue Type: Bug > Environment: Maven 2.0.2 > Latest Jar checkout > Reporter: Michael Böckling > Assignee: Mike Perham > Fix For: 2.1 > > Attachments: jarsign-patch.txt, MJAR-27-maven-jar-plugin.diff, > MJAR-27-maven-jar-plugin.patch, MJAR-27-maven-jar-plugin.patch > > > 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 was sent by Atlassian JIRA (v6.1.6#6162)