[
http://jira.codehaus.org/browse/MNG-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118681
]
Vincent Siveton commented on MNG-3327:
--------------------------------------
see thread on dev@
http://www.nabble.com/Publishing-Plugin-Sites-%28was%3A-Re%3A-Plugins-sandbox-site%29-td13044546s177.html#a13044546
> Deploy site of SNAPSHOT to a different location than site of release version
> ----------------------------------------------------------------------------
>
> Key: MNG-3327
> URL: http://jira.codehaus.org/browse/MNG-3327
> Project: Maven 2
> Issue Type: Improvement
> Components: Documentation: General
> Reporter: Benjamin Bentmann
>
> This issue is not directly targetted at the Maven core but something general
> the Maven developers should consider since Maven is about best practices:
> It is a bad practice to deploy sites of SNAPSHOTs to the same location as the
> final release version. The ordinary user who runs Maven simply using release
> versions of the plugins should be able to read the corresponding
> documentation, not documentation for a different plugin version. For example,
> take
> http://maven.apache.org/plugins/maven-antrun-plugin/examples/tasksAttributes.html
> which describes a feature of the upcoming release which is not yet
> available. It may take users a while to realize that this documentation is
> for the SNAPSHOT version of the AntRun plugin and hence not usable in a
> production build.
> Therefore, I would suggest to deploy release sites to something like
> maven.apche.org/plugins/maven-X-plugin
> (as now) and the SNAPSHOT site to
> maven.apche.org/plugins/maven-X-plugin/snapshot
> or similar. This should be easy using a profile.
--
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
