[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=all ]

Kenney Westerhof closed MASSEMBLY-118.
--------------------------------------

    Resolution: Fixed

with the latest HEAD of the assembly plugin, this problem cannot be reproduced. 
I recognize that it indeed
was a problem, that why it's not 'closed - cannot reproduce'.

Committed the JUnit tests patch (with attribution) in revision 489633.
(Minor change: removed the unused imports).


> assembly <files> uses maven parent relative path and not the modules relative 
> path
> ----------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-118
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-118
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Baerrach bonDierne
>         Assigned To: Kenney Westerhof
>             Fix For: 2.2
>
>         Attachments: MASSEMBLY-118-patch.txt, MASSEMBLY-118-patch.txt, 
> MASSEMBLY-118-patch.txt, MASSEMBLY-118-patch.txt, Maven Assembly Bug.zip
>
>
> In mvn 2.0.4 if I have an assemly descriptor that has the following:
>       <files>
>               <file>
>                       <source>src/site/apt/index.apt</source>
>                       <outputDirectory></outputDirectory>
>                       <destName>README.txt</destName>
>               </file>
>       </files>
> and a maven project that looks like:
> Maven Assembly Bug
> - pom.xml
> - assembly-bug-module
>   - pom.xml
>   - src/site/apt/index.apt
> with the assembly:assembly bound to the package phase inside 
> assembly-bug-module/pom.xml as
>       <build>
>               <plugins>
>                       <plugin>
>                               <artifactId>maven-assembly-plugin</artifactId>
>                               <executions>
>                                       <execution>
>                                               <id>package-assembly</id>
>                                               <phase>package</phase>
>                                               <goals>
>                                                       <goal>assembly</goal>
>                                               </goals>
>                                               <configuration>
>                                                       <descriptors>
>                                                               <descriptor>
>                                                                       
> src/main/assembly/bin.xml
>                                                               </descriptor>
>                                                       </descriptors>
>                                               </configuration>
>                                       </execution>
>                               </executions>
>                       </plugin>
> then when I run mvn install inside assembly-bug-module:
> assembly-bug-module> mvn install
> the command works fine
> When I run mvn install inside the "Maven Assembly Bug" directory the command 
> will fail
> Maven Assembly Bug> mvn install
> [INFO] [assembly:assembly {execution: package-assembly}]
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Error adding file to archive: <path>\Maven Assembly 
> Bug\src\site\apt\index.apt isn't a file.
> Example project is attached as a zip file.
> Trying to change the descriptor to use ${project.build.sourceDirectory} does 
> not work as this is not resoolved.
> [INFO] Error adding file to archive: <path>\Maven Assembly 
> Bug\assembly-bug-module\${project.build.sourceDirectory}
> \site\apt\index.apt isn't a file.

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

        

Reply via email to