[
https://issues.apache.org/jira/browse/MEAR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193988#comment-16193988
]
Hudson commented on MEAR-171:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-plugins #9148 (See
[https://builds.apache.org/job/maven-plugins/9148/])
[MEAR-171] fixed IT (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1811279])
* (edit) maven-ear-plugin/pom.xml
* (edit) maven-ear-plugin/src/it/settings.xml
* (edit) maven-ear-plugin/src/it/skinny-wars-timestamp/verify.bsh
> Full customization of FileNameMapping is needed
> -----------------------------------------------
>
> Key: MEAR-171
> URL: https://issues.apache.org/jira/browse/MEAR-171
> Project: Maven Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.8
> Reporter: Darryl L. Miles
> Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> What is the logic with the seemingly non-standard conversion groupId by
> replacing '.' with '-' in the "full" mode ? Surely this mode should have
> been called "full-with-groupId-rewrite".
> The purpose of this decision should have been documented in the code, someone
> needs to do so or make this format obsolete.
> Alternately the field should look at the maven-war-plugin and the ability to
> support mapping like:
> {noformat}
> @{groupId}@.@{artifactId}@@{dashClassifier?}@-@{version}@.@{extension}@
> {noformat}
> Also the $\{project.finalName} and $\{project.name} would be useful (taken
> out of the dependency's own POM, not the EAR project).
> If this unusual replacement of groupId is required, then maybe
> @\{groupIdReplaceDots}@ can be provided.
> The problem is that the names used are IMPORTANT to know and automate because
> it maybe necessary to place them on the Class-Path in MANIFEST.MF files.
> This non-standard choice needs to be explained because it really is
> non-intuitive and there are no other mechanisms across the maven plugins to
> manage and rewrite Class-Path values in accordance with this convention.
> There is on the other hand clear ways to configure a project and decide on
> the output file names on a project by project basis. This is what should be
> the default, what the project itself decided it wanted to be called like
> $\{project.finalName}.
> The Maven documentation should include complete example of this "full"
> behaviour along with explanation of why it is useful to the user.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
