You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steve Moyer (JIRA)" <ji...@codehaus.org> on 2013/05/28 21:07:52 UTC
[jira] (MEAR-172) Enhance the exception thrown when the EAR plugin
can not map an included artifact
Steve Moyer created MEAR-172:
--------------------------------
Summary: Enhance the exception thrown when the EAR plugin can not map an included artifact
Key: MEAR-172
URL: https://jira.codehaus.org/browse/MEAR-172
Project: Maven 2.x Ear Plugin
Issue Type: Improvement
Reporter: Steve Moyer
Attachments: patch.txt
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira