We should definitely fix this, both in the GPG and in Nexus. Currently it expects all files to be signed and this is the first one we've come across that wasn't signed. I'll disable the rule now until it's sorted out and close the repo for you.
Stephen, what ended up being the fix for the rest of the sigs? This morning it was complaining about all the sigs. On Tue, Jan 12, 2010 at 5:53 PM, Wendy Smoak <wsm...@gmail.com> wrote: > On Tue, Jan 12, 2010 at 9:43 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: >> 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. > > If it's going in the repo, I'd like to see it signed... but this > hasn't been happening up to now, so it probably shouldn't block this > release. > > The archetype catalog is another file that may be a problem, I noticed > it wasn't signed in a recent Struts release. > > Is the list of files that require a signature configurable? > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
