You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2009/10/14 14:22:26 UTC
[jira] Closed: (MJAVADOC-267) Allow changing the
reportOutputDirectory from the commandline
[ http://jira.codehaus.org/browse/MJAVADOC-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MJAVADOC-267.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.6.1
Assignee: Vincent Siveton
fixed in [r824995|http://svn.apache.org/viewvc?rev=824995&view=rev] snapshot deployed
> Allow changing the reportOutputDirectory from the commandline
> -------------------------------------------------------------
>
> Key: MJAVADOC-267
> URL: http://jira.codehaus.org/browse/MJAVADOC-267
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Improvement
> Affects Versions: 2.6
> Reporter: Dirk Olmes
> Assignee: Vincent Siveton
> Fix For: 2.6.1
>
> Attachments: reportOutputDirectory.patch
>
>
> We run the javadoc:aggregate task from the CI server to publish javadocs for a certain release. It's not possible now to specifiy the reportOutputDirectory from the commandline by running
> mvn -DreportOutputDirectory=/dest/dir javadoc:aggregate
> Instead, you have to put this config in a profile/property which exposes too much environment specific info in the pom.
> The attached simple patch allows for specifying the reportOutputDirectory on the cmdline while preserving existing behaviour.
--
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