On 29/04/2010, sebb <[email protected]> wrote:
> On 26/04/2010, sebb <[email protected]> wrote:
> > On 26/04/2010, Jochen Wiedmann <[email protected]> wrote:
> > > On Mon, Apr 26, 2010 at 5:48 PM, sebb <[email protected]> wrote:
> > > > On 26/04/2010, Jochen Wiedmann <[email protected]> wrote:
> > > >> I'd query [email protected] for the recommended procedure.
>
>
> The initial suggestion was to use Nexus and regenerate the checksums that way.
>
> Someone from Sonatype said it required manual intervention and offered
> to fix the checksums in central, which they have now done.
>
> For completeness, I think I should update the copies in the Apache
> repo too. Unless I hear otherwise, I'll do this in a day or two.
FYI more feedback from d...@maven.
The procedure seems to be:
1) Update the Apache release repo with the fixed hashes ("forge" in Maven-speak)
2) File a JIRA issue at http://jira.codehaus.org/browse/MEV to get the
hashes propagated to central.
The Maven devs point out that hash syntax problems should become a
rarity as more forges use repository managers.
>
> > > >>
> > > >
> > > > OK, will do, but Commons procedure might be different from the
> recommendation.
> > >
> > >
> > > The central Maven repository is not maintained by Commons. We should
> > > follow the general rules, not make our own.
> > >
> >
> >
> > Unless Commons wishes to impose additional restrictions, which is what
> > I meant but failed to write.
> >
> > But it seems that is not the case.
> >
> > >
> > > --
> >
> > >
> > > Germanys national anthem is the most boring in the world - how telling!
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
