maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuomas Kiviaho (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MDEP-211) Possibility to prepend groupId to dependencies
Date Thu, 04 Jun 2009 12:38:42 GMT

    [ http://jira.codehaus.org/browse/MDEP-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179290#action_179290
] 

Tuomas Kiviaho edited comment on MDEP-211 at 6/4/09 7:36 AM:
-------------------------------------------------------------

I'm struggling with similar problem between this plugin goal and assembly plugins output using
outputFileNameMapping of a dependencySet. 

In my opinion the filename mapping capability is desirable because it gives total freedom
and removes hassle with stripVersion, prefix, localRepoProperty, outputAbsoluteArtifactFilename,
fileSeparator (and prependGroupId). 

Backwards compatibility can be maintained if there would be a default outputFileNameMapping
which changes as per scenario selected with above parameters and overtakes when explicitly
defined. What assembly plugin also needs is a way to determine whether or not ${artifact.groupId}
is in legacy or default repository mode that would in turn use fileSeparator

      was (Author: tuomas_kiviaho):
    I'm struggling with similar problem between this plugin goal and assembly plugins output
using outputFileNameMapping of a dependencySet. 

In my opinion the filename mapping capability is desirable because it gives total freedom
and removes hassle with stripVersion, prefix, localRepoProperty, outputAbsoluteArtifactFilename
(and prependGroupId). 

Backwards compatibility can be maintained if there would be a default outputFileNameMapping
which changes as per scenario selected with above parameters and overtakes when explicitly
defined. What assembly plugin also needs is a way to determine whether or not ${artifact.groupId}
is in legacy or default repository mode.
  
> Possibility to prepend groupId to dependencies
> ----------------------------------------------
>
>                 Key: MDEP-211
>                 URL: http://jira.codehaus.org/browse/MDEP-211
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Improvement
>          Components: build-classpath, copy-dependencies
>    Affects Versions: 2.2
>            Reporter: Oumar Aziz OUATTARA
>            Assignee: Brian Fox
>         Attachments: add_parameter_prepend_groupId.patch
>
>
> Hi, 
> I would like to use the dependency plugin to copy dependencies including the groupId
in the destination filename. This is to be able afterward to classify the plugins based on
their groupId. 
> It can also avoid a scenario like two dependencies with different groupIds and the same
ArtifactId to collide when doing the copy.
> For this I propose a new configuration parameter "prependGroupId".
> See attached patch for more details.

-- 
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

        

Mime
View raw message