Re: [ALL][COMPRESS-18] Fixing hash file syntax in Maven repo

[sebb <se...@gmail.com>]

On 29/04/2010, sebb <se...@gmail.com> wrote:
> On 29/04/2010, sebb <se...@gmail.com> wrote:
>  > On 26/04/2010, sebb <se...@gmail.com> wrote:
>  >  > On 26/04/2010, Jochen Wiedmann <jo...@gmail.com> wrote:
>  >  >  > On Mon, Apr 26, 2010 at 5:48 PM, sebb <se...@gmail.com> wrote:
>  >  >  >  > On 26/04/2010, Jochen Wiedmann <jo...@gmail.com> wrote:
>  >  >  >  >> I'd query dev@maven.apache.org 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 dev@Maven.
>
>  The procedure seems to be:
>
>  1) Update the Apache release repo with the fixed hashes ("forge" in Maven-speak)

I've now done this.

>  2) File a JIRA issue at http://jira.codehaus.org/browse/MEV to get the
>  hashes propagated to central.

No need in this case, as someone already regenerated the hashes on 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: dev-unsubscribe@commons.apache.org
>  >  >  >  For additional commands, e-mail: dev-help@commons.apache.org
>  >  >  >
>  >  >  >
>  >  >
>  >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org