You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Thomas Vandahl <tv...@apache.org> on 2007/06/16 20:45:32 UTC
Still no go, was: Re: JCS 1.3 not in m1-repo
Thomas Vandahl wrote:
> We decided to fix it for now, but to go with org.apache.jcs for further
> releases. Could you please check if everything is ok now?
I fixed the pom and re-signed it. The dates of the files in the listing
suggest that the new versions have been mirrored. However the links in
the maven1 repo still point into the wild. Is still something wrong? The
report shows the same problem as before, which can't be as I removed the
offending line...
Bye, Thomas.
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Henning Schmiedehausen <he...@apache.org>.
Hi,
thanks for the clarification. I think it is actually, what I meant (the
m2 repo is canonical and the m1 accesses are redirected to m2), but I
explained it wrong. I meant that the m2 repo has the canonical
information and the m1 repo is just a facade to it.
Best regards
Henning
On Sat, 2007-06-23 at 10:20 -0700, Carlos Sanchez wrote:
> On 6/23/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > Yes, looks good now. Thank you.
> >
> > (You are always talking about m1-m2 conversion tool. In this case, it
> > converts the m2 POM to m1, isn't it?)
>
>
> no, the m1 repo is converted to the m2 repo and all requests to m1 are
> redirected to m2. jcs was in the m1 repo but couldn't be converted to
> m2, that's what you saw it, but as the file requests are redirected to
> m2 where it didn't exist it failed
>
>
> >
> > Best regards
> > Henning
> >
> >
> > On Fri, 2007-06-22 at 12:45 -0700, Carlos Sanchez wrote:
> > > fixed now
> > >
> > > the m1-m2 conversion tool was throwing out of memory exceptions
> > >
> > > On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > > > Few hours have passed and nothing has changed. It seems that there is
> > > > still a problem.
> > > >
> > > > Best regards
> > > > Henning
> > > >
> > > >
> > > >
> > > > Carlos Sanchez schrieb:
> > > > > seems that I missed these emails, I have removed the old broken pom
> > > > > and in around 4-8 hours the new one should be there and correctly
> > > > > converted to m2
> > > > >
> > > > > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> > > > >> Thomas Vandahl wrote:
> > > > >> > Thomas Vandahl wrote:
> > > > >> >> We decided to fix it for now, but to go with org.apache.jcs for
> > > > >> further
> > > > >> >> releases. Could you please check if everything is ok now?
> > > > >> >
> > > > >> > I fixed the pom and re-signed it. The dates of the files in the listing
> > > > >> > suggest that the new versions have been mirrored. However the links in
> > > > >> > the maven1 repo still point into the wild. Is still something wrong?
> > > > >> The
> > > > >> > report shows the same problem as before, which can't be as I removed
> > > > >> the
> > > > >> > offending line...
> > > > >> >
> > > > >> > Bye, Thomas.
> > > > >> >
> > > > >> Anybody?
> > > > >>
> > > > >> The jar still cannot be loaded from the maven1-repository.
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
>
>
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Henning Schmiedehausen <he...@apache.org>.
Hi,
thanks for the clarification. I think it is actually, what I meant (the
m2 repo is canonical and the m1 accesses are redirected to m2), but I
explained it wrong. I meant that the m2 repo has the canonical
information and the m1 repo is just a facade to it.
Best regards
Henning
On Sat, 2007-06-23 at 10:20 -0700, Carlos Sanchez wrote:
> On 6/23/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > Yes, looks good now. Thank you.
> >
> > (You are always talking about m1-m2 conversion tool. In this case, it
> > converts the m2 POM to m1, isn't it?)
>
>
> no, the m1 repo is converted to the m2 repo and all requests to m1 are
> redirected to m2. jcs was in the m1 repo but couldn't be converted to
> m2, that's what you saw it, but as the file requests are redirected to
> m2 where it didn't exist it failed
>
>
> >
> > Best regards
> > Henning
> >
> >
> > On Fri, 2007-06-22 at 12:45 -0700, Carlos Sanchez wrote:
> > > fixed now
> > >
> > > the m1-m2 conversion tool was throwing out of memory exceptions
> > >
> > > On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > > > Few hours have passed and nothing has changed. It seems that there is
> > > > still a problem.
> > > >
> > > > Best regards
> > > > Henning
> > > >
> > > >
> > > >
> > > > Carlos Sanchez schrieb:
> > > > > seems that I missed these emails, I have removed the old broken pom
> > > > > and in around 4-8 hours the new one should be there and correctly
> > > > > converted to m2
> > > > >
> > > > > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> > > > >> Thomas Vandahl wrote:
> > > > >> > Thomas Vandahl wrote:
> > > > >> >> We decided to fix it for now, but to go with org.apache.jcs for
> > > > >> further
> > > > >> >> releases. Could you please check if everything is ok now?
> > > > >> >
> > > > >> > I fixed the pom and re-signed it. The dates of the files in the listing
> > > > >> > suggest that the new versions have been mirrored. However the links in
> > > > >> > the maven1 repo still point into the wild. Is still something wrong?
> > > > >> The
> > > > >> > report shows the same problem as before, which can't be as I removed
> > > > >> the
> > > > >> > offending line...
> > > > >> >
> > > > >> > Bye, Thomas.
> > > > >> >
> > > > >> Anybody?
> > > > >>
> > > > >> The jar still cannot be loaded from the maven1-repository.
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Carlos Sanchez <ca...@apache.org>.
On 6/23/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Yes, looks good now. Thank you.
>
> (You are always talking about m1-m2 conversion tool. In this case, it
> converts the m2 POM to m1, isn't it?)
no, the m1 repo is converted to the m2 repo and all requests to m1 are
redirected to m2. jcs was in the m1 repo but couldn't be converted to
m2, that's what you saw it, but as the file requests are redirected to
m2 where it didn't exist it failed
>
> Best regards
> Henning
>
>
> On Fri, 2007-06-22 at 12:45 -0700, Carlos Sanchez wrote:
> > fixed now
> >
> > the m1-m2 conversion tool was throwing out of memory exceptions
> >
> > On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > > Few hours have passed and nothing has changed. It seems that there is
> > > still a problem.
> > >
> > > Best regards
> > > Henning
> > >
> > >
> > >
> > > Carlos Sanchez schrieb:
> > > > seems that I missed these emails, I have removed the old broken pom
> > > > and in around 4-8 hours the new one should be there and correctly
> > > > converted to m2
> > > >
> > > > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> > > >> Thomas Vandahl wrote:
> > > >> > Thomas Vandahl wrote:
> > > >> >> We decided to fix it for now, but to go with org.apache.jcs for
> > > >> further
> > > >> >> releases. Could you please check if everything is ok now?
> > > >> >
> > > >> > I fixed the pom and re-signed it. The dates of the files in the listing
> > > >> > suggest that the new versions have been mirrored. However the links in
> > > >> > the maven1 repo still point into the wild. Is still something wrong?
> > > >> The
> > > >> > report shows the same problem as before, which can't be as I removed
> > > >> the
> > > >> > offending line...
> > > >> >
> > > >> > Bye, Thomas.
> > > >> >
> > > >> Anybody?
> > > >>
> > > >> The jar still cannot be loaded from the maven1-repository.
> > > >>
> > > >>
> > > >
> > > >
> > >
> >
> >
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Carlos Sanchez <ca...@apache.org>.
On 6/23/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Yes, looks good now. Thank you.
>
> (You are always talking about m1-m2 conversion tool. In this case, it
> converts the m2 POM to m1, isn't it?)
no, the m1 repo is converted to the m2 repo and all requests to m1 are
redirected to m2. jcs was in the m1 repo but couldn't be converted to
m2, that's what you saw it, but as the file requests are redirected to
m2 where it didn't exist it failed
>
> Best regards
> Henning
>
>
> On Fri, 2007-06-22 at 12:45 -0700, Carlos Sanchez wrote:
> > fixed now
> >
> > the m1-m2 conversion tool was throwing out of memory exceptions
> >
> > On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > > Few hours have passed and nothing has changed. It seems that there is
> > > still a problem.
> > >
> > > Best regards
> > > Henning
> > >
> > >
> > >
> > > Carlos Sanchez schrieb:
> > > > seems that I missed these emails, I have removed the old broken pom
> > > > and in around 4-8 hours the new one should be there and correctly
> > > > converted to m2
> > > >
> > > > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> > > >> Thomas Vandahl wrote:
> > > >> > Thomas Vandahl wrote:
> > > >> >> We decided to fix it for now, but to go with org.apache.jcs for
> > > >> further
> > > >> >> releases. Could you please check if everything is ok now?
> > > >> >
> > > >> > I fixed the pom and re-signed it. The dates of the files in the listing
> > > >> > suggest that the new versions have been mirrored. However the links in
> > > >> > the maven1 repo still point into the wild. Is still something wrong?
> > > >> The
> > > >> > report shows the same problem as before, which can't be as I removed
> > > >> the
> > > >> > offending line...
> > > >> >
> > > >> > Bye, Thomas.
> > > >> >
> > > >> Anybody?
> > > >>
> > > >> The jar still cannot be loaded from the maven1-repository.
> > > >>
> > > >>
> > > >
> > > >
> > >
> >
> >
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Henning Schmiedehausen <he...@apache.org>.
Yes, looks good now. Thank you.
(You are always talking about m1-m2 conversion tool. In this case, it
converts the m2 POM to m1, isn't it?)
Best regards
Henning
On Fri, 2007-06-22 at 12:45 -0700, Carlos Sanchez wrote:
> fixed now
>
> the m1-m2 conversion tool was throwing out of memory exceptions
>
> On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > Few hours have passed and nothing has changed. It seems that there is
> > still a problem.
> >
> > Best regards
> > Henning
> >
> >
> >
> > Carlos Sanchez schrieb:
> > > seems that I missed these emails, I have removed the old broken pom
> > > and in around 4-8 hours the new one should be there and correctly
> > > converted to m2
> > >
> > > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> > >> Thomas Vandahl wrote:
> > >> > Thomas Vandahl wrote:
> > >> >> We decided to fix it for now, but to go with org.apache.jcs for
> > >> further
> > >> >> releases. Could you please check if everything is ok now?
> > >> >
> > >> > I fixed the pom and re-signed it. The dates of the files in the listing
> > >> > suggest that the new versions have been mirrored. However the links in
> > >> > the maven1 repo still point into the wild. Is still something wrong?
> > >> The
> > >> > report shows the same problem as before, which can't be as I removed
> > >> the
> > >> > offending line...
> > >> >
> > >> > Bye, Thomas.
> > >> >
> > >> Anybody?
> > >>
> > >> The jar still cannot be loaded from the maven1-repository.
> > >>
> > >>
> > >
> > >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Henning Schmiedehausen <he...@apache.org>.
Yes, looks good now. Thank you.
(You are always talking about m1-m2 conversion tool. In this case, it
converts the m2 POM to m1, isn't it?)
Best regards
Henning
On Fri, 2007-06-22 at 12:45 -0700, Carlos Sanchez wrote:
> fixed now
>
> the m1-m2 conversion tool was throwing out of memory exceptions
>
> On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > Few hours have passed and nothing has changed. It seems that there is
> > still a problem.
> >
> > Best regards
> > Henning
> >
> >
> >
> > Carlos Sanchez schrieb:
> > > seems that I missed these emails, I have removed the old broken pom
> > > and in around 4-8 hours the new one should be there and correctly
> > > converted to m2
> > >
> > > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> > >> Thomas Vandahl wrote:
> > >> > Thomas Vandahl wrote:
> > >> >> We decided to fix it for now, but to go with org.apache.jcs for
> > >> further
> > >> >> releases. Could you please check if everything is ok now?
> > >> >
> > >> > I fixed the pom and re-signed it. The dates of the files in the listing
> > >> > suggest that the new versions have been mirrored. However the links in
> > >> > the maven1 repo still point into the wild. Is still something wrong?
> > >> The
> > >> > report shows the same problem as before, which can't be as I removed
> > >> the
> > >> > offending line...
> > >> >
> > >> > Bye, Thomas.
> > >> >
> > >> Anybody?
> > >>
> > >> The jar still cannot be loaded from the maven1-repository.
> > >>
> > >>
> > >
> > >
> >
>
>
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Carlos Sanchez <ca...@apache.org>.
fixed now
the m1-m2 conversion tool was throwing out of memory exceptions
On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Few hours have passed and nothing has changed. It seems that there is
> still a problem.
>
> Best regards
> Henning
>
>
>
> Carlos Sanchez schrieb:
> > seems that I missed these emails, I have removed the old broken pom
> > and in around 4-8 hours the new one should be there and correctly
> > converted to m2
> >
> > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> >> Thomas Vandahl wrote:
> >> > Thomas Vandahl wrote:
> >> >> We decided to fix it for now, but to go with org.apache.jcs for
> >> further
> >> >> releases. Could you please check if everything is ok now?
> >> >
> >> > I fixed the pom and re-signed it. The dates of the files in the listing
> >> > suggest that the new versions have been mirrored. However the links in
> >> > the maven1 repo still point into the wild. Is still something wrong?
> >> The
> >> > report shows the same problem as before, which can't be as I removed
> >> the
> >> > offending line...
> >> >
> >> > Bye, Thomas.
> >> >
> >> Anybody?
> >>
> >> The jar still cannot be loaded from the maven1-repository.
> >>
> >>
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Carlos Sanchez <ca...@apache.org>.
fixed now
the m1-m2 conversion tool was throwing out of memory exceptions
On 6/22/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Few hours have passed and nothing has changed. It seems that there is
> still a problem.
>
> Best regards
> Henning
>
>
>
> Carlos Sanchez schrieb:
> > seems that I missed these emails, I have removed the old broken pom
> > and in around 4-8 hours the new one should be there and correctly
> > converted to m2
> >
> > On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> >> Thomas Vandahl wrote:
> >> > Thomas Vandahl wrote:
> >> >> We decided to fix it for now, but to go with org.apache.jcs for
> >> further
> >> >> releases. Could you please check if everything is ok now?
> >> >
> >> > I fixed the pom and re-signed it. The dates of the files in the listing
> >> > suggest that the new versions have been mirrored. However the links in
> >> > the maven1 repo still point into the wild. Is still something wrong?
> >> The
> >> > report shows the same problem as before, which can't be as I removed
> >> the
> >> > offending line...
> >> >
> >> > Bye, Thomas.
> >> >
> >> Anybody?
> >>
> >> The jar still cannot be loaded from the maven1-repository.
> >>
> >>
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Henning Schmiedehausen <he...@apache.org>.
Few hours have passed and nothing has changed. It seems that there is
still a problem.
Best regards
Henning
Carlos Sanchez schrieb:
> seems that I missed these emails, I have removed the old broken pom
> and in around 4-8 hours the new one should be there and correctly
> converted to m2
>
> On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
>> Thomas Vandahl wrote:
>> > Thomas Vandahl wrote:
>> >> We decided to fix it for now, but to go with org.apache.jcs for
>> further
>> >> releases. Could you please check if everything is ok now?
>> >
>> > I fixed the pom and re-signed it. The dates of the files in the listing
>> > suggest that the new versions have been mirrored. However the links in
>> > the maven1 repo still point into the wild. Is still something wrong?
>> The
>> > report shows the same problem as before, which can't be as I removed
>> the
>> > offending line...
>> >
>> > Bye, Thomas.
>> >
>> Anybody?
>>
>> The jar still cannot be loaded from the maven1-repository.
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Henning Schmiedehausen <he...@apache.org>.
Few hours have passed and nothing has changed. It seems that there is
still a problem.
Best regards
Henning
Carlos Sanchez schrieb:
> seems that I missed these emails, I have removed the old broken pom
> and in around 4-8 hours the new one should be there and correctly
> converted to m2
>
> On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
>> Thomas Vandahl wrote:
>> > Thomas Vandahl wrote:
>> >> We decided to fix it for now, but to go with org.apache.jcs for
>> further
>> >> releases. Could you please check if everything is ok now?
>> >
>> > I fixed the pom and re-signed it. The dates of the files in the listing
>> > suggest that the new versions have been mirrored. However the links in
>> > the maven1 repo still point into the wild. Is still something wrong?
>> The
>> > report shows the same problem as before, which can't be as I removed
>> the
>> > offending line...
>> >
>> > Bye, Thomas.
>> >
>> Anybody?
>>
>> The jar still cannot be loaded from the maven1-repository.
>>
>>
>
>
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Carlos Sanchez <ca...@apache.org>.
seems that I missed these emails, I have removed the old broken pom
and in around 4-8 hours the new one should be there and correctly
converted to m2
On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> Thomas Vandahl wrote:
> > Thomas Vandahl wrote:
> >> We decided to fix it for now, but to go with org.apache.jcs for further
> >> releases. Could you please check if everything is ok now?
> >
> > I fixed the pom and re-signed it. The dates of the files in the listing
> > suggest that the new versions have been mirrored. However the links in
> > the maven1 repo still point into the wild. Is still something wrong? The
> > report shows the same problem as before, which can't be as I removed the
> > offending line...
> >
> > Bye, Thomas.
> >
> Anybody?
>
> The jar still cannot be loaded from the maven1-repository.
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Carlos Sanchez <ca...@apache.org>.
seems that I missed these emails, I have removed the old broken pom
and in around 4-8 hours the new one should be there and correctly
converted to m2
On 6/18/07, Thomas Vandahl <tv...@apache.org> wrote:
> Thomas Vandahl wrote:
> > Thomas Vandahl wrote:
> >> We decided to fix it for now, but to go with org.apache.jcs for further
> >> releases. Could you please check if everything is ok now?
> >
> > I fixed the pom and re-signed it. The dates of the files in the listing
> > suggest that the new versions have been mirrored. However the links in
> > the maven1 repo still point into the wild. Is still something wrong? The
> > report shows the same problem as before, which can't be as I removed the
> > offending line...
> >
> > Bye, Thomas.
> >
> Anybody?
>
> The jar still cannot be loaded from the maven1-repository.
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Thomas Vandahl wrote:
>> We decided to fix it for now, but to go with org.apache.jcs for further
>> releases. Could you please check if everything is ok now?
>
> I fixed the pom and re-signed it. The dates of the files in the listing
> suggest that the new versions have been mirrored. However the links in
> the maven1 repo still point into the wild. Is still something wrong? The
> report shows the same problem as before, which can't be as I removed the
> offending line...
>
> Bye, Thomas.
>
Anybody?
The jar still cannot be loaded from the maven1-repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Still no go, was: Re: JCS 1.3 not in m1-repo
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Thomas Vandahl wrote:
>> We decided to fix it for now, but to go with org.apache.jcs for further
>> releases. Could you please check if everything is ok now?
>
> I fixed the pom and re-signed it. The dates of the files in the listing
> suggest that the new versions have been mirrored. However the links in
> the maven1 repo still point into the wild. Is still something wrong? The
> report shows the same problem as before, which can't be as I removed the
> offending line...
>
> Bye, Thomas.
>
Anybody?
The jar still cannot be loaded from the maven1-repository.