[ http://jira.codehaus.org/browse/MNG-2479?page=comments#action_71435 ]
Ian Springer commented on MNG-2479:
---
Hmm, I'm not sure I agree with this. If it was desired to override the default
filename for transitive deps, this could be achieved by explicitly declaring
the transitive deps in the J2EE pom. In your example, W's pom could explicitly
declare A, in addition to B, in order to specify packaging names for both. The
same thing would basically be true for plugin-by-plugin defined configuration
schemes. That is, transitive artifacts would only need to be explicitly defined
if you needed to override the packaging name or some other setting specific to
that artifact. For me, one of the biggest pros of Maven is consistency in how
things are done. By not having a central way of specifying packaging filenames
(and packaging target directories), you end up with ten different plugins doing
it ten different ways, or not doing it at all.
> add support for optional 'packagingName' element in dependency blocks
> -
>
> Key: MNG-2479
> URL: http://jira.codehaus.org/browse/MNG-2479
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
>Affects Versions: 2.0.4
>Reporter: Ian Springer
> Assigned To: Brett Porter
>
> The various deployment artifact types (war, ear, sar, etc.) package their
> dependencies within the target archive during the package phase. For example,
> the war plugin includes jar dependencies within WEB-INF/lib, and the ear
> plugin includes jar and J2EE dependencies at the top level. Sometimes it is
> not desirable to package the dependencies with their full Maven-repo-style
> names (i.e. artifactName-version.xar). In particular, the version component
> is often not desired. Currently, some plugins provide a way to rename these
> dependency artifacts when they are packaged (e.g. the ear plugin), and others
> do not (e.g. the war plugin), making it necessary to use an antrun or
> dependency plugin hack to rename the artifacts as desired. I think it would
> be much nicer if there was a standard way to specify a "packaging name" (or
> whatever other name makes sense) for a dependency in its dependency block in
> the pom. Then all plugins that package their dependencies could leverage this
> standard setting.
> Here is an example of a war dependency declared in an ear pom:
>
> org.jboss.on
> on-enterprise-gui-portal
> 2.0-SNAPSHOT
> war
> on-portal
>
> This would cause the war to be bundled in the ear with the filename
> "on-portal.war", instead of the default
> on-enterprise-gui-portal-2.0-SNAPSHOT.war.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
