On 29/04/2010, at 10:50 PM, sebb wrote:
> On 29/04/2010, Brett Porter wrote:
>> The correct one for reporting problems (vs new uploads) is:
>> http://jira.codehaus.org/browse/MEV
>>
>> In general, you want to make sure it is fixed at the source first if it's an
>> imported forge like Apache's
On 29/04/2010, Brett Porter wrote:
> The correct one for reporting problems (vs new uploads) is:
> http://jira.codehaus.org/browse/MEV
>
> In general, you want to make sure it is fixed at the source first if it's an
> imported forge like Apache's.
So, is the correct procedure as follows:
1) U
The correct one for reporting problems (vs new uploads) is:
http://jira.codehaus.org/browse/MEV
In general, you want to make sure it is fixed at the source first if it's an
imported forge like Apache's.
- Brett
On 29/04/2010, at 9:45 PM, Juven Xu wrote:
> I think people can create tasks here:
I think people can create tasks here:
http://jira.codehaus.org/browse/MAVENUPLOAD
or at Sonatype:
https://issues.sonatype.org/browse/OSSRH
On Thu, Apr 29, 2010 at 4:12 PM, sebb wrote:
> OK thanks very much.
>
> If this problem recurs with other projects, is there a formal means of
> reporting i
OK thanks very much.
If this problem recurs with other projects, is there a formal means of
reporting it?
e.g. via an issue tracker?
On 29/04/2010, Juven Xu wrote:
> checksums on pgp signautes are deleted.
>
>
> On Wed, Apr 28, 2010 at 11:34 PM, sebb wrote:
>
> > On 28/04/2010, Juven Xu wrot
checksums on pgp signautes are deleted.
On Wed, Apr 28, 2010 at 11:34 PM, sebb wrote:
> On 28/04/2010, Juven Xu wrote:
> > On Wed, Apr 28, 2010 at 11:05 PM, sebb wrote:
> >
> > > On 28/04/2010, Juven Xu wrote:
> > > > you can use these shell scripts:
> > > >
> > > > find . -type f | xarg
On 28/04/2010, Juven Xu wrote:
> On Wed, Apr 28, 2010 at 11:05 PM, sebb wrote:
>
> > On 28/04/2010, Juven Xu wrote:
> > > you can use these shell scripts:
> > >
> > > find . -type f | xargs -i sh -c 'sha1sum {} | cut -d " " -f1 > {}.sha1'
> > > find . -type f | xargs -i sh -c 'md5sum {} |
On Wed, Apr 28, 2010 at 11:05 PM, sebb wrote:
> On 28/04/2010, Juven Xu wrote:
> > you can use these shell scripts:
> >
> > find . -type f | xargs -i sh -c 'sha1sum {} | cut -d " " -f1 > {}.sha1'
> > find . -type f | xargs -i sh -c 'md5sum {} | cut -d " " -f1 > {}.md5'
>
> Thanks, I have alrea
On 28/04/2010, Juven Xu wrote:
> you can use these shell scripts:
>
> find . -type f | xargs -i sh -c 'sha1sum {} | cut -d " " -f1 > {}.sha1'
> find . -type f | xargs -i sh -c 'md5sum {} | cut -d " " -f1 > {}.md5'
Thanks, I have already created the fixed hashes.
[BTW, the find command above ne
you can use these shell scripts:
find . -type f | xargs -i sh -c 'sha1sum {} | cut -d " " -f1 > {}.sha1'
find . -type f | xargs -i sh -c 'md5sum {} | cut -d " " -f1 > {}.md5'
release artifacts and their hashes in central will never be updated unless
manual fix is needed
if your artifacts' hashes
On 26/04/2010, sebb wrote:
> What is the recommended procedure for fixing hash files in a Maven
> repo that have the wrong syntax?
I have seen the reply about using Nexus, but if the project does not
use Nexus, what is the procedure?
If I update the hashes in the release repo will these be prop
What is the recommended procedure for fixing hash files in a Maven
repo that have the wrong syntax?
For example:
file.tar.gz.sha1:
file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB 52F3
3B4C
The hash is correct, but not all tools can process the hash when i
Use Nexus and run rebuild maven metadata.
On Mon, Apr 26, 2010 at 11:56 AM, sebb wrote:
> What is the recommended procedure for fixing hash files in a Maven
> repo that have the wrong syntax?
>
> For example:
>
> file.tar.gz.sha1:
> file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB 52F3
>
What is the recommended procedure for fixing hash files in a Maven
repo that have the wrong syntax?
For example:
file.tar.gz.sha1:
file.tar.gz: B886 07FA D17D 06C2 7D67 01D6 E7E6 56BB 52F3
3B4C
The hash is correct, but not all tools can process the hash when it
14 matches
Mail list logo
