[ http://jira.codehaus.org/browse/MASSEMBLY-98?page=all ]
Edwin Punzalan updated MASSEMBLY-98: ------------------------------------ Attachment: MASSEMBLY-98-maven-assembly-plugin.patch > Assembly groupVersionAlignment excludes affects all other > groupVersionAlignment > ------------------------------------------------------------------------------- > > Key: MASSEMBLY-98 > URL: http://jira.codehaus.org/browse/MASSEMBLY-98 > Project: Maven 2.x Assembly Plugin > Type: Bug > Versions: 2.1 > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Attachments: MASSEMBLY-98-maven-assembly-plugin.patch > > > Setting this in your assembly xml: > {code} > <repository> > <groupVersionAlignments> > <groupVersionAlignment> > <id>group-a</id> > <version>1.0</version> > </groupVersionAlignment> > <groupVersionAlignment> > <id>group-b</id> > <version>2.0</version> > <excludes> > <exclude>artifact-a</exclude> > </excludes> > </groupVersionAlignment> > </groupVersionAlignments> > </repository> > {code} > what happens is that if there is an artifact with groupId=group-a and > artifactId=artifact-a, it gets excluded even though artifact-a is declared to > be excluded in group-b. What effectively happens is something like this: > {code} > <repository> > <groupVersionAlignments> > <groupVersionAlignment> > <id>group-a</id> > <version>1.0</version> > <excludes> > <exclude>artifact-a</exclude> > </excludes> > </groupVersionAlignment> > <groupVersionAlignment> > <id>group-b</id> > <version>2.0</version> > <excludes> > <exclude>artifact-a</exclude> > </excludes> > </groupVersionAlignment> > </groupVersionAlignments> > </repository> > {code} -- 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