The root cause seems to be that m-gpg-p does not consider that project.artifact may have multiple entries (specifically the site metadata)
We can argue that the site needs to be decoupled from releasing, but as the site descriptor is one of the artifacts of a project (as opposed to the site) then the site descriptor needs to be pushed to the repo too... therefore m-site-p is correct to attach it (but possibly incorrect attaching it directly to project.artifact) In any case MGPG-19 reflects this crazy model of attaching artifacts to a project because m-gpg-p does not look in this (frankly unknown to me) other way of attaching an artifact. If we are to fix this it will require re-deploying all the parents after deploying a new m-gpg-p... all of which I suspect will require turning off gpg validation on r.a.o first -Stephen 2010/1/12 Stephen Connolly <stephen.alan.conno...@gmail.com>: > Fair enough, but we cannot make releases as things currently stand > > 2010/1/12 Jason van Zyl <ja...@sonatype.com>: >> The site stuff needs to be completely decoupled from releases. It such a >> horrible coupling and causes nothing but problems. Release and the >> documentation that goes along with it are completely separate. >> >> On 2010-01-12, at 12:08 PM, Daniel Kulp wrote: >> >>> >>> 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 >>> >> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> ---------------------------------------------------------- >> >> >> --------------------------------------------------------------------- >> 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
