Any feed back on this issue - anyone? I see conflicting things in the source code - things like how the <files> lists ARE expanded with things from the mavenProject object, not just a filters file.
-----Original Message----- From: EJ Ciramella [mailto:[email protected]] Sent: Friday, February 20, 2009 3:21 PM To: Maven Users List Subject: RE: Using the <filtered> option within an assembly descriptor I think I've discovered what's tripping me up a bit here. Does this filtering take into consideration properties defined within the mavenProject object or ONLY stuff pass in via the filtering file. I'm referencing this page in particular: http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/fi ltering-some-distribution-files.html "All the above files are in the root directory of the project but only the README and the NOTICE files should be filtered. The property file used to filter these are files is found in src/assemble/filter.properties." However, there is some conflicting documatation up there - in one place, it suggests filters only exist for <files> but it's clearly there in <fileSets>. Mick - I just saw your reply, and no, I've not set up <filters> in my pom. I've been under the impression (until right now) that the filtering that the assembly plugin did factored in any of the mavenProject properties - which apparently it doesn't. Am I correct? -----Original Message----- From: EJ Ciramella [mailto:[email protected]] Sent: Friday, February 20, 2009 3:06 PM To: [email protected] Subject: Using the <filtered> option within an assembly descriptor Hello again list, I'm struggling to get this thing working. I'm trying my hardest to not process files (for a war project) once to the target directory then AGAIN into the final assembly location. So I'm using mvn assembly:directory but I don't see any of the tokens expanded for the files when inside the descriptor, I have something like this: <fileSet> <directory>src/main/resources/java-properties</directory> <outputDirectory>somedir</outputDirectory> <useStrictFiltering>true</useStrictFiltering> <lineEnding>unix</lineEnding> <filtered>true</filtered> <includes> <include>hibernate.properties</include> </includes> </fileSet> The resulting hibernate.properties file still has ${stuff} type properties left in there. Any suggestions? --------------------------------------------------------------------- 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]
