You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2015/04/30 23:02:07 UTC

[jira] [Commented] (MDEP-485) unpack-dependencies should be able to use subdirectories per classifier

    [ https://issues.apache.org/jira/browse/MDEP-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522263#comment-14522263 ] 

Karl Heinz Marbaise commented on MDEP-485:
------------------------------------------

Can you create a full example and describe more in detail how you imagine the result would be? Best is to attach such example to this issue ?

> unpack-dependencies should be able to use subdirectories per classifier
> -----------------------------------------------------------------------
>
>                 Key: MDEP-485
>                 URL: https://issues.apache.org/jira/browse/MDEP-485
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>          Components: unpack-dependencies
>    Affects Versions: 2.10
>            Reporter: Dirk Rudolph
>            Priority: Minor
>             Fix For: waiting-for-feedback
>
>
> When using classifiers to build environment specific artefacts, aggregating them to for example a single deployment unit (in my case its an rpm file, using the rpm plugin) would be easier when there would be a configuration option to unpack all dependencies to a subdirectory per classifier.
> {code}
> <configuration>
>  <useSubDirectoryPerClassifier>true</useSubDirectoryPerClassifier>
> </configuration>
> {code}
> In this case we could easily unpack all dependencies build for development environment to a single place. Adding a new artefact would require adding a dependency and *not* changing the plugin configuration for the build of the deployment unit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)