[
http://jira.codehaus.org/browse/MASSEMBLY-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265738#action_265738
]
Kelly Davis commented on MASSEMBLY-394:
---------------------------------------
Just to clarify. I set some properties using properties that are read from a
props file using the properties-maven-plugin as follows:
<properties>
<jetty.home>${myapp.jetty.home}</jetty.home>
</properties>
myapp.jetty.home is defined in a property file (config.properties) read in by
the properties-maven-plugin (attached to the initialize phase)
If I try to use ${jetty.home} for <outputDirectory> it just defaults to the
project build directory. If I set jetty.home to a constant, it works properly.
The strange thing is that the assembly plugin correctly uses the properties in
config.properties when filtering files.
Using ${project.properties.*} doesn't work. I have tested in 3.0.3 & 2.2.1 with
the same result.
> Property filtering does not work inside the outputDirectory element content
> ---------------------------------------------------------------------------
>
> Key: MASSEMBLY-394
> URL: http://jira.codehaus.org/browse/MASSEMBLY-394
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-3
> Environment: Maven version: 2.0.10
> Java version: 1.5.0_15
> Ubuntu 8.10
> OS name: "linux" version: "2.6.27-11-generic" arch: "i386" Family: "unix"
> Reporter: Keith Wedinger
> Assignee: John Casey
>
> Inside my POM, I have the following property defined:
> <properties>
> <clump.name>b2b_oba</clump.name>
> </properties>
> Inside my assembly descriptor, I am attempting to use the property above as
> well as project defined properties to filter the outputDirectory element
> content contained within <files><file>. The relevant descriptor snippet is
> below:
> <files>
> <file>
>
> <source>${clump.codejar.output.directory}/${project.name}.jar</source>
>
> <outputDirectory>${project.name}/jars/${clump.name}/${clump.version.dir}</outputDirectory>
> </file>
> </files>
> After running mvn assembly:assembly, the resultant outputDirectory content
> remains as follows. None of the properties are replaced with their
> corresponding values.
> <outputDirectory>${project.name}/jars/${project.name}/${clump.version.dir}</outputDirectory>
> maven-assembly-plugin version 2.1 does not have this issue. When I use
> version 2.1, property filtering on the outputDirectory works correctly.
--
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
