[MEAR-172] Enhance the exception thrown when the EAR plugin can not map an included artifact

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9
• Flags: Patch
• Assignee: Robert Scholte
• Reporter: Steve Moyer
• Created: 28/May/13 14:07
• Updated: 05/Apr/15 14:44
• Resolved: 14/Nov/13 16:17

Description

If unknown artifact types are included in the hierarchy of an EAR project's dependency, The ArtifactTypeMappingService will throw an UnknownArtifactTypeException with a message that looks something like "Unknown artifact type[test-jar]". Since the artifact type to be mapped is passed as a string, the getStandardType(final String type) method can't generate a message that includes the artifactId.

The attached patch includes changes to the EarModuleFactory that catches and rethrows the UnknownArtifactTypeException while appending the artifactId to the exception's message. The changes result in a message that looks something like "Unknown artifact type[test-jar] for jboss-as-ejb3", making debugging a failed EAR build much easier.