[
https://jira.codehaus.org/browse/MEAR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335721#comment-335721
]
Steve Moyer commented on MEAR-172:
----------------------------------
Thanks for managing the project! I'm very happy to share patches when I'm also
so reliant on the coterie of Maven plugins to automate my builds.
> 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 Ear Plugin
> Issue Type: Improvement
> Reporter: Steve Moyer
> Assignee: Robert Scholte
> Fix For: 2.9
>
> 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
