Filtering problems with assembly plugin called from parent POM

[adamd1234 <ad...@gmail.com>]

Hi all,

I have a most peculiar case within my compilation that is causing my
assembly plug-in to not filter certain files. First of all I bound my
assembly phase to the package phase for ease of assembling artefacts.  The
POM is defined as so:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-assembly-plugin</artifactId>
                <executions>
                    <execution>
                        <id>assemble</id>
                        <phase>package</phase>
                        <goals>
                            <goal>single</goal>
                        </goals>
                        <configuration>
                            <descriptors>
                               
<descriptor>src/main/assembly/package.xml</descriptor>
                            </descriptors>
                            <skipAssembly>false</skipAssembly>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

The package.xml contains assembly defines and the most prominent and the one
regarding my problem is the resource set defined as so:

                <!-- Script files -->
		<fileSet>
			<directory>src/main/resources</directory>
			<lineEnding>unix</lineEnding>
			<filtered>true</filtered>
			<outputDirectory>bin</outputDirectory>
			<fileMode>0755</fileMode>
                       <directoryMode>0755</directoryMode>
			<includes>
				<include>*.sh</include>
				<include>*.bat</include>
			</includes>
		</fileSet>

Now here is the problem; when I do a mvn package on this artefact filtering
occurs normally but when I do the same on its parent everything works as
normal but filtering is skipped (note that this didn't occur when assembly
phase was unbound and called separately). What even weirder is that if I
explicitly define every file to be filtered by using <file> tag not filesets
then filtering occurs normally from the POM. Does anyone have an idea of why
this coul be happening?

Regards
Adam.
-- 
View this message in context: http://old.nabble.com/Filtering-problems-with-assembly-plugin-called-from-parent-POM-tp27148460p27148460.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org