[
https://issues.apache.org/struts/browse/WW-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46588#action_46588
]
Wes Wannemacher commented on WW-3108:
-------------------------------------
I think you can do -
-Dgoals=deploy
when you are running release:perform and it won't try to upload a site.
> Trying to release the struts-master artifact will deploy files to the
> struts.apache.org website
> -----------------------------------------------------------------------------------------------
>
> Key: WW-3108
> URL: https://issues.apache.org/struts/browse/WW-3108
> Project: Struts 2
> Issue Type: Bug
> Components: Build Management
> Reporter: Wes Wannemacher
> Fix For: 2.1.8
>
>
> When I was releasing the struts-master artifact, at the 'release:perform'
> step, a bunch of files were generated and pushed out the
> people.apache.org:/www/struts.apache.org. This effectively overwrote our site
> with a basic maven-esque site. We typically manage our site using the maven
> site plugin and keep that source in a different folder in SVN. We need to
> update the struts/maven/pom/pom.xml file so that release:perform does not do
> this in the future. We could update the docs here -
> http://struts.apache.org/2.x/docs/creating-and-signing-a-struts-21x-distribution.html
> , but I would rather we avoid making different artifacts have different
> release instructions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
