On 12/3/05, Steve Cohen <[EMAIL PROTECTED]> wrote: > Sheesh, the release process has gotten much hairier since I last did it! > 5 hours and I'm still not all the way there. And this was supposed to > be a simple release. > > Phooey. > > I decided that that easiest way to do this "simple" release fixing ONLY > the 1.3 compatibility problem would be to work from a branch cut at > 1_4_0. And that is how I built it. > > Now however, I get to step 10 Publish updated website and maven is > failing. Can this even work when deploying from a branch and not the trunk? > <snip/> > > [echo] Generating the StatCvs Report... > statcvs:init: > > statcvs:generate: > statcvs:init-variables: > statcvs:parse-connection: > [echo] Using connection: > scm:svn:http://svn.apache.org/repos/asf/jakarta/commons/proper/net/trunk > > BUILD FAILED > File...... > file:/home/scohen/.maven/plugins/maven-statcvs-plugin-2.5/plugin.jelly > Element... ant:fail > Line...... 103 > Column.... 19 > Unknown SCM method: 'svn' > Total time: 19 seconds > Finished at: Sat Dec 03 12:34:56 CST 2005 > <snap/>
Sorry, I can't pinpoint whats going on, though I have two suggestions: 1) Turn off the statcvs report (the trunk doesn't have it anyway, and the error message seems to come out of there) 2) If you can generate the site locally (maven site) but can't deploy it -- while you sort it out -- a clearly suboptimal solution that you could consider is to tar/zip the generated site (maven site) and manually expand in the siteDirectory (to avoid undue delay in the releasing process). -Rahul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
