You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Brian Minchau <mi...@ca.ibm.com> on 2008/04/01 07:29:33 UTC
Re: Uploading Xalan 2.7.1 to apache repository
I Carlos.
Yes I can copy things there. I'm not exactly sure which jars you want but
I'll look into it tomorrow.
- Brian
"Carlos Sanchez"
<carlos@apache.or
g> To
Sent by: Brian Minchau/Toronto/IBM@IBMCA
carlossg@gmail.co cc
m "J. Daniel Kulp" <dk...@apache.org>
Subject
Uploading Xalan 2.7.1 to apache
03/31/2008 10:16 repository
PM
Hi Brian,
Re XALANJ-2417 if you could please put the jar and jar with sources
(optionally) in
/www/people.apache.org/repo/m1-ibiblio-rsync-repository/xalan/jars so
the other projects can use it automatically (maven, ant tasks,
ivy,...) with md5/sha1 and GPG signature. Apache projects usually do
it themselves, sometimes I had put them myself but recently the
requirement of being GPG signed by somebody in the project makes that
not possible. For any questions you can ask me or reach
repository@apache.org
If not, Daniel please raise the issue in repository@apache.org to see
how to proceed.
Thanks
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Uploading Xalan 2.7.1 to apache repository
Posted by Steve Loughran <st...@gmail.com>.
well then, better add a feature req to ivy. Will the new staging
server move all the checksums back to the conventional layout
On Sat, Feb 14, 2009 at 10:21 AM, Brett Porter <br...@apache.org> wrote:
> This is the openssl output format. Maven supports this in addition to the
> other one, however when Maven generates them it uses the checksum on its
> own.
>
> On 14/02/2009, at 12:22 AM, Steve Loughran wrote:
>
>> Is the sha1 sum for this artifact correctly formatted?
>>
>> http://repo2.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.sha1
>>
>> is
>> SHA1(xalan-2.7.1.jar)= 75f1d83ce27bab5f29fff034fc74aa9f7266f22a
>>
>> which breaks Ivy
>>
>> [ivy:resolve] :: problems summary ::
>> [ivy:resolve] :::: WARNINGS
>> [ivy:resolve] [FAILED ] xalan#xalan;2.7.1!xalan.jar: invalid
>> sha1: expected=sha1(xalan-2.7.1.jar)=
>> computed=75f1d83ce27bab5f29fff034fc74aa9f7266f22a (1268ms)
>> [ivy:resolve] [FAILED ] xalan#xalan;2.7.1!xalan.jar: (0ms)
>> [ivy:resolve] ==== local: tried
>>
>> I would have expected it to look like the sources sha1
>> b1f9b407f3593c99ae2b137bb0733761fcee6595 xalan-2.7.1-sources.jar
>>
>> Not looked @other repos to see if the problem is consistent. If it is,
>> I would propose correcting and pushing out new SHA1 files.
>>
>>
>>
>> On Tue, Apr 1, 2008 at 5:29 AM, Brian Minchau <mi...@ca.ibm.com> wrote:
>>>
>>> I Carlos.
>>> Yes I can copy things there. I'm not exactly sure which jars you want but
>>> I'll look into it tomorrow.
>>>
>>> - Brian
>>>
>>>
>>>
>>>
>>> "Carlos Sanchez"
>>> <carlos@apache.or
>>> g> To
>>> Sent by: Brian Minchau/Toronto/IBM@IBMCA
>>> carlossg@gmail.co cc
>>> m "J. Daniel Kulp" <dk...@apache.org>
>>> Subject
>>> Uploading Xalan 2.7.1 to apache
>>> 03/31/2008 10:16 repository
>>> PM
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Hi Brian,
>>>
>>> Re XALANJ-2417 if you could please put the jar and jar with sources
>>> (optionally) in
>>> /www/people.apache.org/repo/m1-ibiblio-rsync-repository/xalan/jars so
>>> the other projects can use it automatically (maven, ant tasks,
>>> ivy,...) with md5/sha1 and GPG signature. Apache projects usually do
>>> it themselves, sometimes I had put them myself but recently the
>>> requirement of being GPG signed by somebody in the project makes that
>>> not possible. For any questions you can ask me or reach
>>> repository@apache.org
>>>
>>> If not, Daniel please raise the issue in repository@apache.org to see
>>> how to proceed.
>>>
>>> Thanks
>>>
>>> --
>>> I could give you my word as a Spaniard.
>>> No good. I've known too many Spaniards.
>>> -- The Princess Bride
>>>
>>>
>>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
Re: Uploading Xalan 2.7.1 to apache repository
Posted by Brett Porter <br...@apache.org>.
This is the openssl output format. Maven supports this in addition to
the other one, however when Maven generates them it uses the checksum
on its own.
On 14/02/2009, at 12:22 AM, Steve Loughran wrote:
> Is the sha1 sum for this artifact correctly formatted?
>
> http://repo2.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.sha1
>
> is
> SHA1(xalan-2.7.1.jar)= 75f1d83ce27bab5f29fff034fc74aa9f7266f22a
>
> which breaks Ivy
>
> [ivy:resolve] :: problems summary ::
> [ivy:resolve] :::: WARNINGS
> [ivy:resolve] [FAILED ] xalan#xalan;2.7.1!xalan.jar: invalid
> sha1: expected=sha1(xalan-2.7.1.jar)=
> computed=75f1d83ce27bab5f29fff034fc74aa9f7266f22a (1268ms)
> [ivy:resolve] [FAILED ] xalan#xalan;2.7.1!xalan.jar: (0ms)
> [ivy:resolve] ==== local: tried
>
> I would have expected it to look like the sources sha1
> b1f9b407f3593c99ae2b137bb0733761fcee6595 xalan-2.7.1-sources.jar
>
> Not looked @other repos to see if the problem is consistent. If it is,
> I would propose correcting and pushing out new SHA1 files.
>
>
>
> On Tue, Apr 1, 2008 at 5:29 AM, Brian Minchau <mi...@ca.ibm.com>
> wrote:
>> I Carlos.
>> Yes I can copy things there. I'm not exactly sure which jars you
>> want but
>> I'll look into it tomorrow.
>>
>> - Brian
>>
>>
>>
>>
>> "Carlos Sanchez"
>> <carlos@apache.or
>>
>> g> To
>> Sent by: Brian Minchau/Toronto/IBM@IBMCA
>>
>> carlossg@gmail.co cc
>> m "J. Daniel Kulp" <dkulp@apache.org
>> >
>>
>> Subject
>> Uploading Xalan 2.7.1 to apache
>> 03/31/2008 10:16 repository
>> PM
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi Brian,
>>
>> Re XALANJ-2417 if you could please put the jar and jar with sources
>> (optionally) in
>> /www/people.apache.org/repo/m1-ibiblio-rsync-repository/xalan/jars so
>> the other projects can use it automatically (maven, ant tasks,
>> ivy,...) with md5/sha1 and GPG signature. Apache projects usually do
>> it themselves, sometimes I had put them myself but recently the
>> requirement of being GPG signed by somebody in the project makes that
>> not possible. For any questions you can ask me or reach
>> repository@apache.org
>>
>> If not, Daniel please raise the issue in repository@apache.org to see
>> how to proceed.
>>
>> Thanks
>>
>> --
>> I could give you my word as a Spaniard.
>> No good. I've known too many Spaniards.
>> -- The Princess Bride
>>
>>
>>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
Re: Uploading Xalan 2.7.1 to apache repository
Posted by Steve Loughran <st...@gmail.com>.
Is the sha1 sum for this artifact correctly formatted?
http://repo2.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.sha1
is
SHA1(xalan-2.7.1.jar)= 75f1d83ce27bab5f29fff034fc74aa9f7266f22a
which breaks Ivy
[ivy:resolve] :: problems summary ::
[ivy:resolve] :::: WARNINGS
[ivy:resolve] [FAILED ] xalan#xalan;2.7.1!xalan.jar: invalid
sha1: expected=sha1(xalan-2.7.1.jar)=
computed=75f1d83ce27bab5f29fff034fc74aa9f7266f22a (1268ms)
[ivy:resolve] [FAILED ] xalan#xalan;2.7.1!xalan.jar: (0ms)
[ivy:resolve] ==== local: tried
I would have expected it to look like the sources sha1
b1f9b407f3593c99ae2b137bb0733761fcee6595 xalan-2.7.1-sources.jar
Not looked @other repos to see if the problem is consistent. If it is,
I would propose correcting and pushing out new SHA1 files.
On Tue, Apr 1, 2008 at 5:29 AM, Brian Minchau <mi...@ca.ibm.com> wrote:
> I Carlos.
> Yes I can copy things there. I'm not exactly sure which jars you want but
> I'll look into it tomorrow.
>
> - Brian
>
>
>
>
> "Carlos Sanchez"
> <carlos@apache.or
> g> To
> Sent by: Brian Minchau/Toronto/IBM@IBMCA
> carlossg@gmail.co cc
> m "J. Daniel Kulp" <dk...@apache.org>
> Subject
> Uploading Xalan 2.7.1 to apache
> 03/31/2008 10:16 repository
> PM
>
>
>
>
>
>
>
>
>
> Hi Brian,
>
> Re XALANJ-2417 if you could please put the jar and jar with sources
> (optionally) in
> /www/people.apache.org/repo/m1-ibiblio-rsync-repository/xalan/jars so
> the other projects can use it automatically (maven, ant tasks,
> ivy,...) with md5/sha1 and GPG signature. Apache projects usually do
> it themselves, sometimes I had put them myself but recently the
> requirement of being GPG signed by somebody in the project makes that
> not possible. For any questions you can ask me or reach
> repository@apache.org
>
> If not, Daniel please raise the issue in repository@apache.org to see
> how to proceed.
>
> Thanks
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
>
>