Why does the site descriptor need to be "released" as part of the plugin? Why not release surefire without it?
It's definitely a bug, but I'm failing to see why it's a blocker for now. Dan On Tue January 12 2010 11:56:28 am Stephen Connolly wrote: > I've raised http://jira.codehaus.org/browse/MGPG-19 to track the root > cause. > > A temporary work around would be to disable GPG validation on r.a.o > > -Stephen > > P.S. > > I'm blocked from releasing Surefire 2.5 due to this issue > > 2010/1/12 Stephen Connolly <stephen.alan.conno...@gmail.com>: > > For some reason the site descriptor does not get a signature generated > > by the gpg plugin. > > > > As r.a.o now requires all artifacts to be signed, it would appear to > > be impossible to close a staged repository. > > > > Or do other people have information to the contrary? > > > > -Stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
