[
http://jira.codehaus.org/browse/MASSEMBLY-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207676#action_207676
]
John Cheng commented on MASSEMBLY-455:
--------------------------------------
Thanks. That worked.
I tried adding the /assembly/fileSets/fileSet/outputDirectory element into the
example jar-with-dependencies.xml shown in the documentation
(http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html)
and tested it out.
The assembly descriptors in the documentation is definitely different than what
is included in the maven-assembly-plugin-2.2-beta-2.jar. And the actual
descriptors in the jar refers to directories like "target/classes" instead of
${project.build.outputDirectory}.
> 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
