On Sunday 16 August 2009 11:22:53 pm Wendy Smoak wrote: > On Sun, Aug 16, 2009 at 12:02 PM, Wes Wannemacher<w...@wantii.com> wrote: > > No Martin, my point is that the problem is that one of the steps deployed > > stuff to a place where it shouldn't go. I'm sure that each of the steps > > works fine, but when issuing this command - > > > > mvn release:perform > > > > for the struts-master (or was it struts-parent), it generated a skeletal > > site and pushed it out to the location served by the struts.apache.org > > domain. I have a few theories as to why it did this for me, despite the > > docs on the release process indicating that it is the right thing to > > do... For instance, maybe since I am a bit overzealous about keeping ssh > > keys in place so that scps, etc. happen w/o trouble. > > The default goals for release:perform are 'deploy site-deploy'. > > http://maven.apache.org/plugins/maven-release-plugin/examples/perform-relea >se.html > > I haven't looked at it, but you might consider > - changing the site url in <distributionManagement> so the parent pom > isn't pointed at the top level site. > - configuring the goals for the release plugin so it doesn't publish > the site automatically
The fix I posted to SVN was option two... The downside to this is that I think everything down the chain will inherit from it, right? Although, the same would go for option one. Maybe it wouldn't be bad to do both options, then configure distributionManagement in the site artifact. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
