Awesome. That fixed it, thanks! -----Original Message----- From: Bracewell, Robert [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 11:06 To: Maven Users List Subject: RE: assembly filtering not working in multi-module set up
Yes I have had the same issue in multi-module projects using filesets. I had to change the fileset to be <files> and it worked. The Maven assembly plugin documentation page states "Filtering is only enabled inside <files>..." -----Original Message----- From: Richard Chamberlain [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 11:00 To: Maven Users List Subject: assembly filtering not working in multi-module set up Hi, I've got a start script in my project that reads java -cp lib/myartefact-${pom.version}.jar .... and my assembly.xml is set to filter it: pom.xml ... <plugin> <artifactId>maven-assembly-plugin</artifactId> <executions> <execution> <id>make-assembly</id> <phase>package</phase> <goals> <goal>attached</goal> </goals> </execution> </executions> <configuration> <descriptors> <descriptor>/src/main/assembly/kit.xml</descriptor> </descriptors> </configuration> </plugin> ... Kit.xml ... <fileSet> <directory>src/main/bin</directory> <outputDirectory>/</outputDirectory> <fileMode>755</fileMode> <filtered>true</filtered> </fileSet> ... So when I run clean install, the file gets filtered to java -cp lib/myartefact-4.4.2.jar .... however i have a multi-module project: parent +-core +-moduleA +-moduleB And when I run the build from the parent my start script doesn't get filtered! Has anyone seen anything like this before? Thanks, Richard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
