You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2013/05/25 02:41:20 UTC

[jira] [Resolved] (MPOM-42) prepare svnpubsub documentation publication to /plugins-archives/-LATEST

     [ https://issues.apache.org/jira/browse/MPOM-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy resolved MPOM-42.
-------------------------------

    Resolution: Fixed
    
> prepare svnpubsub documentation publication to /plugins-archives/<artifactId>-LATEST
> ------------------------------------------------------------------------------------
>
>                 Key: MPOM-42
>                 URL: https://issues.apache.org/jira/browse/MPOM-42
>             Project: Maven POMs
>          Issue Type: Improvement
>          Components: maven-plugins
>    Affects Versions: MAVEN-PLUGINS-24
>            Reporter: Hervé Boutemy
>            Assignee: Hervé Boutemy
>             Fix For: MAVEN-PLUGINS-25
>
>
> site staging for each plugin will simply be done with
>   mvn -Preporting site-deploy
> if a svn commit issue happens, restarting svnpubsub publication:
>   mvn scm-publish:publish-scm
> then release staging:
>   svn cp https://svn.apache.org/repos/infra/websites/production/maven/content/plugins-archives/[artifactId]>-LATEST https://svn.apache.org/repos/infra/websites/production/maven/content/plugins-archives/[artifactId]-[version] -m 'staging [artifactId] [version] documentation'
> then final release documentation publication:
>   svnmucc -U https://svn.apache.org/repos/infra/websites/production/maven/content rm plugins/[artifactId] cp HEAD plugins-archives/[artifactId]-[version] plugins/[artifactId] -m 'publishing [artifactId] [version] documentation'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira