[ 
https://jira.codehaus.org/browse/MASSEMBLY-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316084#comment-316084
 ] 

Hannes Kogler edited comment on MASSEMBLY-394 at 12/21/12 6:01 AM:
-------------------------------------------------------------------

I don't know what this blacklist "feature" is for?

Can anybody please describe why this makes sense?

The other critical point is, that on the one hand the own defined properties 
from the pom.xml aren't interpolated in the assembly descriptors tags ( 
"outputFileNameMapping", "outputDirectoryMapping", "outputDirectory" ), but on 
the other hand the interpolation within those tags work without any problems 
with the default variables like ${artifact.groupId}.


so where is the difference?
-> <outputDirectory>${artifact.groupId}</outputDirectory> => works!
-> <outputDirectory>${project.properties.anyPropFromPom}</outputDirectory> => 
won't be interpolated!?

                
      was (Author: ntshko):
    I don't know what this blacklist "feature" is for?

Can anybody please describe why this makes sense?

The other critical point is, that on the one hand the own defined properties 
from the pom.xml aren't interpolated in the assembly descriptors tags ( 
"outputFileNameMapping", "outputDirectoryMapping", "outputDirectory" ), but on 
the other hand the interpolation within those tags work without any problems 
with the default variables like ${artifact.groupId}.
                  
> Property filtering does not work inside the outputDirectory element content
> ---------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-394
>                 URL: https://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, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to