[jira] Updated: (MASSEMBLY-150) Clarify or fix relative scoping in assembly descriptor to be module centric or location of mvn execution

["John Casey (JIRA)" <ji...@codehaus.org>]

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

John Casey updated MASSEMBLY-150:
---------------------------------

    Fix Version/s:     (was: 2.2)
                   2.2-beta-5

review the use of project.getBasedir() vs. just using the assumed basedir when handling fileItem sources.

> Clarify or fix <file> relative scoping in assembly descriptor to be module centric or location of mvn execution
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-150
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-150
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: windows xp
>            Reporter: Harold Shinsato
>             Fix For: 2.2-beta-5
>
>
> According to http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html, the assembly descriptor's <file> source is supposed to be absolute or relative from the module's directory.  This works when I execute mvn in the module directory.  But when I run it from a top level super project, it seems to run from that higher level project.  This isn't how the <fileSet> works, which we were using before, but we needed to set filtering to true, which caused this to break.
> So this is how we have to write this to make this work from the top level, but it breaks when running the assembly from this directory.
>     <files>
>         <file>
>             <source>fileutil/src/main/scripts/FileUploadUtility.bat</source>
>             <outputDirectory>file-utility</outputDirectory>
>             <filtered>true</filtered>
>         </file>
>     </files>
> This is how it used to be specified, where it worked both from the top level and from the subdirectory:
>     <fileSets>
>         <fileSet>
>             <directory>../fileutil</directory>
>             <outputDirectory>file-utility</outputDirectory>
>             <includes>
>                 <include>FileUploadUtility.bat</include>
>             </includes>
>         </fileSet>
>     </fileSets>
> Hopefully this won't make a difference, but we've plugged our assembly into the execution of the package phase.  This is copied from the pom.xml of the module.
>   <build>
>     <plugins>
>       <plugin>
>         <artifactId>maven-assembly-plugin</artifactId>
>         <configuration>
>           <descriptors>
>             <descriptor>src/main/assembly/dist.xml</descriptor>
>           </descriptors>
>         </configuration>
>         <executions>
>           <execution>
>             <goals>
>               <goal>attached</goal>
>             </goals>
>             <phase>package</phase>
>           </execution>
>         </executions>
>       </plugin>
>     </plugins>
>   </build>

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