You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Lim (JIRA)" <ji...@codehaus.org> on 2009/07/06 10:06:22 UTC
[jira] Closed: (MASSEMBLY-429) Incorrect documentation with regards
to baseDirectory
[ http://jira.codehaus.org/browse/MASSEMBLY-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Lim closed MASSEMBLY-429.
-------------------------------
Resolution: Not A Bug
Fix Version/s: 2.2-beta-3
2.2-beta-4
Ignore. Error on my part.
> Incorrect documentation with regards to baseDirectory
> -----------------------------------------------------
>
> Key: MASSEMBLY-429
> URL: http://jira.codehaus.org/browse/MASSEMBLY-429
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-3, 2.2-beta-4
> Reporter: David Lim
> Priority: Trivial
> Fix For: 2.2-beta-4, 2.2-beta-3
>
>
> The site documentation at http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html mentions that baseDirectory defaults to ${project.build.finalName} if includeBaseDirectory is true (which is the documented default).
> But regardless of whether I omit includeBaseDirectory for explicitly configure "true" or "false", the result is that baseDirectory always defaults to "${artifactId}-${version}". I have to explicitly state <baseDirectory>${project.build.finalName}</baseDirectory> to get it to work properly.
--
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