You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Wes Wannemacher (JIRA)" <ji...@apache.org> on 2009/08/11 21:33:59 UTC
[jira] Resolved: (WW-3108) Trying to release the struts-master
artifact will deploy files to the struts.apache.org website
[ https://issues.apache.org/struts/browse/WW-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes Wannemacher resolved WW-3108.
---------------------------------
Resolution: Fixed
I added some configuration to the release plugin that should stop this from happening in the future. Unfortunately this sort of thing is hard to test because I won't know until struts-master gets released again whether or not the fix does the trick. So, if this happens again, someone reopen this issue. Also, I didn't get the svn commit tagged against this JIRA because mvn committed the fix for me at some point while I was trying to make sure that the changes would work. (it committed when I did a `mvn release:rollback`... I had used -DdryRun=true when I did release:prepare, but the rollback must have detected a change and sent it upstream)
> 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.