maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Syedin (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MASSEMBLY-389) ${project.dir} doesnt seem to work
Date Tue, 03 Aug 2010 18:21:32 GMT

    [ http://jira.codehaus.org/browse/MASSEMBLY-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230750#action_230750
] 

Alexander Syedin commented on MASSEMBLY-389:
--------------------------------------------

Martin, support for ${settings.localRepository} is addressed by MASSEMBLY-333

> ${project.dir} doesnt seem to work
> ----------------------------------
>
>                 Key: MASSEMBLY-389
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-389
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>         Environment: mac/ubuntu jdk5 
> I appear to be using ...
> /var/maven2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.2-beta-2/maven-assembly-plugin-2.2-beta-2.jar
>            Reporter: Martin West
>         Attachments: AssemblyBug.zip
>
>
> fileset as per documentation example doesnt work.
> The attached mini project is a subset of the real project. Gives the following error:
> [INFO] [assembly:assembly]
> [INFO] Reading assembly descriptor: src/main/assemble/bin.xml
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to create assembly: Error creating assembly archive zip: You must set at
least one file.
> In the real project the file set does not have any affect. If I replace ${project.build.directory}
with target then it includes the file structure target and its sub directories rather than
the contents of the specified directory. What I expect is that the contents of target/assemble/pdf
appear in the zip as /tis/docs/pdf/ and similarly the contents of the html directory to appear
in the /tis/docs/html folder in the zip.
> The documentation, which is generally good by the usual poor maven standards, is poor
in this area. The design does not appear to very good here ...
> When using a <fileset> <includes> <include> I would have expected it
to follow the ant fileset specification inventing a new model leads to poor usability as most
developers will expect the ant fileset model.

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