[
http://jira.codehaus.org/browse/MASSEMBLY-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-493.
--------------------------------
Resolution: Not A Bug
Assignee: John Casey
If you compare your exclude spec vs. your projects' groupIds, you'll notice
that they don't match. Which is why you'd see the following when you build this
project:
[WARNING] The following patterns were never triggered in this artifact
exclusion filter:
o 'com.med.training:com.med.training.spring.jsf'
If you change the exclude to
'com.med.training.spring:com.med.training.spring.jsf' or even just '*jsf*' this
assembly will probably work.
BTW, new in beta-6 will be a feature for using moduleSets from a child project.
It's called <useAllReactorProjects> and it's used directly inside the
<moduleSet> to allow access to all projects in the current reactor for
selection in that module-set.
If you add appropriate dependencies to the child project to ensure it is sorted
to the end of the build, you can bind the creation of this assembly to the main
build process using assembly:single. This allows your project to be built using
a standard command line: `mvn clean install`.
> Filters do not work in moduleSet
> --------------------------------
>
> Key: MASSEMBLY-493
> URL: http://jira.codehaus.org/browse/MASSEMBLY-493
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-5
> Environment: java version "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) Client VM (build 17.0-b16, mixed mode, sharing)
> Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_21
> Java home: C:\Program Files (x86)\Java\jdk1.6.0_21\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
> Reporter: Greg Snyder
> Assignee: John Casey
> Attachments: multimodule-filter.zip
>
>
> Filtering does not work on a multi-module project. I am trying to exclude
> one sub-module with this descriptor:
> <assembly
>
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
> <id>Install-Package</id>
> <formats>
> <format>dir</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <moduleSets>
> <moduleSet>
> <excludes>
>
> <exclude>com.med.training:com.med.training.spring.jsf</exclude>
> </excludes>
> <binaries>
> <unpack>false</unpack>
> <dependencySets>
> <dependencySet>
> <unpack>false</unpack>
> <scope>compile</scope>
>
> <outputDirectory>dependencies</outputDirectory>
> </dependencySet>
> </dependencySets>
> </binaries>
> </moduleSet>
> </moduleSets>
> <dependencySets>
> <dependencySet>
> <unpack>false</unpack>
> <outputDirectory>dependencies</outputDirectory>
> </dependencySet>
> </dependencySets>
> </assembly>
> However, when I run assembly:assembly the project I want to exclude shows up
> in the assembly. Also, these warning are show in the maven output:
> [INFO] Reading assembly descriptor: assembly.xml
> [WARNING] The following patterns were never triggered in this artifact
> exclusion filter:
> o 'com.med.training:com.med.training.spring.jsf'
> [WARNING] Cannot include project artifact:
> com.med.training:com.med.training.spring:pom:0.0.1-SNAPSHOT; it doesn't have
> an associated file or directory.
> [WARNING] The following patterns were never triggered in this artifact
> exclusion filter:
> o 'com.med.training:com.med.training.spring.jsf'
> I've attached a sample project which has this issue. Run "mvn clean package
> assembly:assembly" on the root pom file to reproduce the issue.
--
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
