You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Edd Steel (JIRA)" <ji...@codehaus.org> on 2008/07/16 12:09:26 UTC
[jira] Created: (MASSEMBLY-340) Filtering doesn't work for
multimodule assembly builds
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
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
[jira] Updated: (MASSEMBLY-340) Filtering doesn't work for
multimodule assembly builds
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-340:
---------------------------------
Fix Version/s: 2.2-beta-3
> 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
> Fix For: 2.2-beta-3
>
>
> 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
[jira] Closed: (MASSEMBLY-340) Filtering doesn't work for
multimodule assembly builds
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ 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