Fix away as you find things that are not right. musachy On Sat, Nov 15, 2008 at 3:19 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 15, 2008 at 1:14 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On Fri, Nov 14, 2008 at 12:29 PM, Musachy Barroso <[EMAIL PROTECTED]> > wrote: > > > >> > https://svn.apache.org/repos/asf/struts/struts2/branches/release_process > > > > The first thing I notice is that the gpg signing is in the default > > build. If you put it in a profile with an id of 'release' then it > > will be activated automatically during the release process. > > ... except that it won't due to this in pluginManagement: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <configuration> > <useReleaseProfile>false</useReleaseProfile> > </configuration> > </plugin> > > The built-in release profile generates the sources and javadocs jars. > It's also useful to put additional things into the 'release' profile, > knowing it will get activated automatically. > > For example, I don't want to have to provide my pgp passphrase every > time I build the project locally, the signing only needs to happen at > release time. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd
