[jira] Closed: (MDEP-87) Include/ExcludeGroupIds only work for one item

["Brian Fox (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MDEP-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox closed MDEP-87.
-------------------------

    Resolution: Cannot Reproduce

I can't find anything wrong here. I did find some extra code that wasn't used that might have thrown you off. Inside the abstractArtifactFeatureFilter, take a look at setExcludes and setIncludes:

    public void setExcludes( String excludeString )
    {
        this.excludeString = excludeString;

        if ( StringUtils.isNotEmpty( excludeString ) )
        {
            this.excludes = Arrays.asList( StringUtils.split( excludeString, "," ) );
        }
    }

    public void setIncludes( String includeString )
    {
        this.includeString = includeString;

        if ( StringUtils.isNotEmpty( includeString ) )
        {
            this.includes = Arrays.asList( StringUtils.split( includeString, "," ) );
        }
    }

I added more specific unit and integration tests. The debug output also displays the count of the tokens, so you can be sure it's tokenizing correctly.


> Include/ExcludeGroupIds only work for one item
> ----------------------------------------------
>
>                 Key: MDEP-87
>                 URL: http://jira.codehaus.org/browse/MDEP-87
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>            Reporter: Jörg Hohwiller
>            Assignee: Brian Fox
>
> From your description excludeGroupIds and some other parameters are supposed to work as comma separated list:
> http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html#excludeGroupIds
> This does NOT work though I would need this feature. I digged in the code and could not find any tokenization of these String parameters.
> Neigther in the AbstractDependency*Mojo nor in the Filters.
> To me it seems that the feature is only specified but not implemented.
> Is there a workaround for this?

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