[ 
https://issues.apache.org/jira/browse/MPOM-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632689#comment-17632689
 ] 

Slawomir Jaranowski commented on MPOM-359:
------------------------------------------

As I know we need two execution for multi module projects
 - one mvn site site:stage
 - second when all modules are staged in stage directory in root project: mvn 
scm-publish:publish-scm

I don't sure if it can work with one execution

 

maybe it is time to support svn deployment is standard site:deploy goal instead 
of using [https://maven.apache.org/plugins/maven-scm-publish-plugin/] 

[~michael-o] what do you think?

> Deploy site also with release:perform
> -------------------------------------
>
>                 Key: MPOM-359
>                 URL: https://issues.apache.org/jira/browse/MPOM-359
>             Project: Maven POMs
>          Issue Type: Improvement
>          Components: maven
>            Reporter: Konrad Windszus
>            Priority: Major
>
> By default {{release:perform}} executes both {{deploy}} and {{site-deploy}} 
> (if the project has a <distributionManagement>/<site> element), compare with 
> https://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html#goals.
>  This default behaviour is overwritten in the ASF parent at 
> https://github.com/apache/maven-apache-parent/blob/a4f3c6400104f711e86342649bb77a3a55f1f97f/pom.xml#L255
>  by a simple {{deploy}} i.e. site is not built and deployed when performing 
> the release.
> As having the staged site available for all Maven releases is reasonable 
> already at the time the vote starts (makes it easy to verify the site) and 
> the staging site is anyhow in a dedicated repository 
> (https://maven.apache.org/developers/website/deploy-component-reference-documentation.html#staging-component-reference-documentation,
>  i.e. not visible to end users) I propose to restore the default behaviour 
> for {{m-r-p}} in the Maven Parent POM.
> This would also require to disable the default binding of 
> https://maven.apache.org/plugins/maven-site-plugin/deploy-mojo.html and 
> instead bind 
> {{https://maven.apache.org/plugins/maven-scm-publish-plugin/publish-scm-mojo.html}}
>  to that phase.
> Then the step 2 from 
> https://maven.apache.org/developers/release/maven-project-release-procedure.html#promote-the-release
>  would be a simple replacement of the final site at 
> https://maven.apache.org/developers/website/deploy-component-reference-documentation.html#publishing-versioned-component-reference-documentation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to