[
https://issues.apache.org/jira/browse/MEAR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959049#comment-17959049
]
Matthias Bünger commented on MEAR-172:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ear-plugin#350|https://github.com/apache/maven-ear-plugin/issues/350].
> Enhance the exception thrown when the EAR plugin can not map an included
> artifact
> ---------------------------------------------------------------------------------
>
> Key: MEAR-172
> URL: https://issues.apache.org/jira/browse/MEAR-172
> Project: Maven EAR Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Reporter: Steve Moyer
> Assignee: Robert Scholte
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
