You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by Sam Ruby <ru...@apache.org> on 2003/05/04 13:24:02 UTC
Re: Build Failure - jakarta-cactus-documentation
Christopher Lenz wrote:
>
> This one is puzzling me. I've just tried the (non-Gump) build on a Linux
> machine, and it is working well.
>
> Note the 'Not logged in' error in the output, which occurs when we try
> to load a another XML file via document(uri), where uri is the absolute
> path to the file.
Is it possible that one of your dependencies has changed (xalan,
perhaps)? You can get access to the jars that gump built here:
http://gump.covalent.net/jars/2003-05-04/
alljars.zip contains everything, or you can download individual jars
individually.
Alternately, would it help if you were given an id on one of the
machines upon which gump is already running? I'm also willing to talk
you through setting up gump on your machine, or even set it up for you
if I am given access.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Build Failure - jakarta-cactus-documentation
Posted by Sam Ruby <ru...@apache.org>.
Christopher Lenz wrote:
>
> Wow that was quick. Thanks a bunch. I guess it's the file:/ protocol in
> the URI that is somehow messing things up, so I've removed it for now.
BUILD SUCCESSFUL
Total time: 35 seconds
It doesn't take long to try out a change...
- Sam Ruby
Re: Build Failure - jakarta-cactus-documentation
Posted by Christopher Lenz <cm...@gmx.de>.
Sam Ruby wrote:
> Christopher Lenz wrote:
>>
>> I'm not even sure if the build also fails on covalent or nagoya. We'll
>> see later today, probably. Would it be possible for you to record the
>> -debug output of the build on rubix, and forward that to me?
>
> http://cvs.apache.org/~rubys/cactus-doc-release.tgz
>
> - Sam Ruby
Wow that was quick. Thanks a bunch. I guess it's the file:/ protocol in
the URI that is somehow messing things up, so I've removed it for now.
--
Christopher Lenz
/=/ cmlenz at gmx.de
Re: Build Failure - jakarta-cactus-documentation
Posted by Sam Ruby <ru...@apache.org>.
Christopher Lenz wrote:
>
> I'm not even sure if the build also fails on covalent or nagoya. We'll
> see later today, probably. Would it be possible for you to record the
> -debug output of the build on rubix, and forward that to me?
http://cvs.apache.org/~rubys/cactus-doc-release.tgz
- Sam Ruby
Re: Build Failure - jakarta-cactus-documentation
Posted by Christopher Lenz <cm...@gmx.de>.
Sam Ruby wrote:
> Christopher Lenz wrote:
>> This one is puzzling me. I've just tried the (non-Gump) build on a
>> Linux machine, and it is working well.
>>
>> Note the 'Not logged in' error in the output, which occurs when we try
>> to load a another XML file via document(uri), where uri is the
>> absolute path to the file.
>
> Is it possible that one of your dependencies has changed (xalan,
I don't think so. The failures started after I changed the uri from a
relative to an absolute path.
> perhaps)? You can get access to the jars that gump built here:
>
> http://gump.covalent.net/jars/2003-05-04/
>
> alljars.zip contains everything, or you can download individual jars
> individually.
>
> Alternately, would it help if you were given an id on one of the
> machines upon which gump is already running? I'm also willing to talk
I'm not even sure if the build also fails on covalent or nagoya. We'll
see later today, probably. Would it be possible for you to record the
-debug output of the build on rubix, and forward that to me?
> you through setting up gump on your machine, or even set it up for you
> if I am given access.
I've set Gump up before, it's only that my linux box currently needs to
be reanimated.
Thanks!
--
Christopher Lenz
/=/ cmlenz at gmx.de
Re: Build Failure - jakarta-cactus-documentation
Posted by Christopher Lenz <cm...@gmx.de>.
Sam Ruby wrote:
> Christopher Lenz wrote:
>> This one is puzzling me. I've just tried the (non-Gump) build on a
>> Linux machine, and it is working well.
>>
>> Note the 'Not logged in' error in the output, which occurs when we try
>> to load a another XML file via document(uri), where uri is the
>> absolute path to the file.
>
> Is it possible that one of your dependencies has changed (xalan,
I don't think so. The failures started after I changed the uri from a
relative to an absolute path.
> perhaps)? You can get access to the jars that gump built here:
>
> http://gump.covalent.net/jars/2003-05-04/
>
> alljars.zip contains everything, or you can download individual jars
> individually.
>
> Alternately, would it help if you were given an id on one of the
> machines upon which gump is already running? I'm also willing to talk
I'm not even sure if the build also fails on covalent or nagoya. We'll
see later today, probably. Would it be possible for you to record the
-debug output of the build on rubix, and forward that to me?
> you through setting up gump on your machine, or even set it up for you
> if I am given access.
I've set Gump up before, it's only that my linux box currently needs to
be reanimated.
Thanks!
--
Christopher Lenz
/=/ cmlenz at gmx.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org