maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MASSEMBLY-340) Filtering doesn't work for multimodule assembly builds
Date Thu, 11 Sep 2008 19:42:49 GMT

     [ http://jira.codehaus.org/browse/MASSEMBLY-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Casey closed MASSEMBLY-340.
--------------------------------

    Resolution: Duplicate

> Filtering doesn't work for multimodule assembly builds
> ------------------------------------------------------
>
>                 Key: MASSEMBLY-340
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-340
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>            Reporter: Edd Steel
>            Assignee: John Casey
>
> I have a script with the following lines
> REM ${project.version}
> java -jar ${artifact.artifactId}-${artifact.version}.${artifact.packaging}
> in one of my modules ("Module A"). The assembly plugin is bound to the package phase
in the Module A POM.
> If I run "mvn clean install" in Module A's directory, the resulting installed bundle
has filtered the script correctly.
> If I run "mvn clean install" in the parent POM, of which Module A is a module, Module
A is built and installed, and the bundle installed has the script without filtering. 
> Relevant debug output:
> [DEBUG] After assembly is interpolated:
> ...
>     <fileSet>
>       <directory>scripts</directory>
>       <lineEnding>unix</lineEnding>
>       <filtered>true</filtered>
>       <outputDirectory></outputDirectory>
>       <includes>
>         <include>*.sh</include>
>       </includes>
>       <fileMode>0750</fileMode>
>     </fileSet>
>     <fileSet>
>       <directory>scripts</directory>
>       <lineEnding>dos</lineEnding>
>       <filtered>true</filtered>
>       <outputDirectory></outputDirectory>
>       <includes>
>         <include>*.cmd</include>
>         <include>*.bat</include>
>       </includes>
>       <fileMode>0750</fileMode>
>     </fileSet>
>     <fileSet>
> ...
> [DEBUG] Adding directory file-set in: D:\projects\project\module-a\scripts to archive
location: 
> [DEBUG] FileSet[] dir perms: 40755 file perms: 100644 lineEndings: unix
> [DEBUG] The archive base directory is 'null'
> [INFO] No files selected for line-ending conversion. Skipping: scripts
> [DEBUG] Adding file-set from directory: 'D:\projects\project\module-a\scripts'
> assembly output directory is: ''
> [DEBUG] Adding directory file-set in: D:\projects\project\module-a\scripts to archive
location: 
> [DEBUG] FileSet[] dir perms: 40755 file perms: 100644 lineEndings: dos
> [DEBUG] The archive base directory is 'null'
> [INFO] No files selected for line-ending conversion. Skipping: scripts
> I don't know if that last [INFO] line is a clue?

-- 
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

        

Mime
View raw message