You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ian Brandt (JIRA)" <ji...@codehaus.org> on 2012/06/18 20:59:21 UTC

[jira] (MDEP-47) Ability to have an includes/excludes feature on the dependency:unpack goal.

    [ https://jira.codehaus.org/browse/MDEP-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301384#comment-301384 ] 

Ian Brandt commented on MDEP-47:
--------------------------------

I have a case where I need to specify quite a few explicit includes (25-ish, but still less than the number of excludes otherwise).  The single {{<includes>}} element as a comma separated {{String}} is a bit unwieldy for this.  Going through the patches it appears this issue started out with a {{String[]}} and nested {{<include>}}/{{<exclude>}} elements.  That syntax would work better for my case.  Also anecdotally I've seen that syntax used more often, e.g. by the maven-resources-plugin, maven-jar-plugin, and maven-compiler-plugin.  

>From the comments above it appears there was some patch discussion carried out elsewhere.  Is there a reason the single {{String}} as comma separated list was preferred?
                
> Ability to have an includes/excludes feature on the dependency:unpack goal.
> ---------------------------------------------------------------------------
>
>                 Key: MDEP-47
>                 URL: https://jira.codehaus.org/browse/MDEP-47
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: New Feature
>          Components: unpack
>            Reporter: Paul Shemansky
>            Assignee: Brian Fox
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: MDED-47-maven-dependency-plugin-2.patch, MDED-47-maven-dependency-plugin-3.patch, MDEP-47-maven-dependency-plugin-4.patch, MDEP-47-maven-dependency-plugin-5.patch, MDEP-47-maven-dependency-plugin.patch, test.zip
>
>
> Perhaps there is another solution that I'm overlooking, and if so... I apologize, but in the dependency-maven-plugin's dependency:unpack goal, it would be quite convenient to have an option to have an includes/excludes capability which did pattern matched unpack resolutions.  I.E.  :
> <!-- files I'd like to unpack -->
> <includes>
> <include>*.class</include>
> </includes>
> <excludes>
> <exclude>*.html</exclude>
> </excludes>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira