You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thanh Thai (JIRA)" <ji...@codehaus.org> on 2010/01/15 00:47:55 UTC

[jira] Commented: (MASSEMBLY-455) Incorrect documentation for Pre-defined Descriptor Files

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

Thanh Thai commented on MASSEMBLY-455:
--------------------------------------

You need to specify the output file directory to replicate the same functionality at least on windows.

For instance:

  <fileSets>
    <fileSet>
      <directory>${project.build.outputDirectory}</directory>
      <outputDirectory>/</outputDirectory>
    </fileSet>
  </fileSets>

> Incorrect documentation for Pre-defined Descriptor Files
> --------------------------------------------------------
>
>                 Key: MASSEMBLY-455
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-455
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>            Reporter: John Cheng
>
> The descriptors at http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html do not match the actual descriptors included in the maven-assembly-plugin-2.2-beta-2.jar file. The documentation use properties such as ${project.build.outputDirectory}, which seems to cause problems in actual descriptor files (on windows, at least, it includes the full absolute path).
> It is not easy to understand how to go about writing custom assembly descriptors.

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