I did try to use the plugin last time, but there's a problem with my security setup, and the plugin doesn't work for me. I'd like to setup a new workstation soon, but it probably won't happen this calendar year.
The underlying problem is that the ASF expects us to sign all the JARs, which complicates the release process, and creates a bar toward other volunteers stepping up and helping. Ironically, the reason we sign the JARs is to help protect the release managers from individual liability. On Dec 4, 2007 9:39 AM, Tomislav Stojcevich <[EMAIL PROTECTED]> wrote: > It does, but from the looks of the release process at > http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html > the release plugin is not being used. > > Even if it were, in the parent pom it has > <useReleaseProfile>false</useReleaseProfile> in the release plugin > configuration so it won't run with that profile for whatever reason. > > It could be changed so that it does run with the release profile > and/or changed so that all required profiles are run "-P > release,all,alljars,pre-assembly". > > That way nobody forgets. Just mvn release:prepare and mvn release:perform. > > Although the build does look a bit more complex so maybe it can't be done. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
