[MJAR-27] jar:sign doesn't check if project produces an artifact

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1
• Environment: Maven 2.0.2; Latest Jar checkout
• Assignee: Mike Perham
• Reporter: Michael Böckling
• Created: 01/Feb/06 12:56
• Updated: 31/Oct/14 13:37
• Resolved: 22/Jun/06 18:43

Description

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...

Issue Links

• is related to: MJAR-29 Artifact name not correctly calculated for EAR
• is related to: MJAR-20 Don't create empty jars