On 27 Jun 07, at 7:45 PM 27 Jun 07, Daniel Kulp wrote:
Maven 2.0.4 had this problem where all the poms ended up with bad sigs
due to the pom changing (pom re-write) during deploy.Maven 2.0.5
fixed that. Did 2.0.6 regress?
No, the POM is still untouched. The license files are still int
Maven 2.0.4 had this problem where all the poms ended up with bad sigs
due to the pom changing (pom re-write) during deploy.Maven 2.0.5
fixed that. Did 2.0.6 regress?
Dan
On Tuesday 26 June 2007 18:28, Jason van Zyl wrote:
> On 26 Jun 07, at 3:09 PM 26 Jun 07, Arnaud HERITIER wrote:
> >
On 26 Jun 07, at 3:09 PM 26 Jun 07, Arnaud HERITIER wrote:
I don't think that it could be problem in the gpg plugin. I
copied/adapted its code in the artifact plugin for m1 and it seems to
work fine (but we don't have to move artifacts between repos)
I'm trying some installs and deploys, and
I don't think that it could be problem in the gpg plugin. I
copied/adapted its code in the artifact plugin for m1 and it seems to
work fine (but we don't have to move artifacts between repos)
Arnaud
On 26/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 26 Jun 07, at 2:23 PM 26 Jun 07, Jason
On 26 Jun 07, at 2:23 PM 26 Jun 07, Jason van Zyl wrote:
On 26 Jun 07, at 1:27 PM 26 Jun 07, Carlos Sanchez wrote:
The checksums and signature don't match the pom
http://jira.codehaus.org/browse/MEV-530
It's not just that it's all of them.
By this I mean POMs. The 2.0.7 Maven parent PO
On 26 Jun 07, at 1:27 PM 26 Jun 07, Carlos Sanchez wrote:
The checksums and signature don't match the pom
http://jira.codehaus.org/browse/MEV-530
It's not just that it's all of them. I checked the staging repository
and the production repository and the signature is bad in both places
a
The checksums and signature don't match the pom
http://jira.codehaus.org/browse/MEV-530
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
-
To u
