On Friday, October 4, 2002, at 12:55 AM, Henri Gomez wrote:
> Steve Downey wrote:
>> On Thursday 03 October 2002 12:14 pm, Henri Gomez wrote:
>>> Steve Downey wrote:
>>>
Actually, with the recent release of commons-logging, we should be
able
to get rid of the explicit LogKit and
Yes, just a blank line before the line indicated in the parsing exception. I
found this trying to move the line number, hoping to find the -- that
shouldn't be there. Putting blanks at the beginning of the file moved the
error line from 307 to 308:
SEVERE: Parse Fatal Error at line 307 column
Steve Downey wrote:
> On Thursday 03 October 2002 12:14 pm, Henri Gomez wrote:
>
>>Steve Downey wrote:
>>
>>>Actually, with the recent release of commons-logging, we should be able
>>>to get rid of the explicit LogKit and Log4J. They're there so as to get a
>>>complete build of commons-logging. T
On Thursday 03 October 2002 12:14 pm, Henri Gomez wrote:
> Steve Downey wrote:
> > Actually, with the recent release of commons-logging, we should be able
> > to get rid of the explicit LogKit and Log4J. They're there so as to get a
> > complete build of commons-logging. Tomcat 5 itself doesn't us
On Thursday, October 3, 2002, at 09:14 AM, Henri Gomez wrote:
> Steve Downey wrote:
>> Actually, with the recent release of commons-logging, we should be
>> able to get rid of the explicit LogKit and Log4J. They're there so as
>> to get a complete build of commons-logging. Tomcat 5 itself doe
On Thursday 03 October 2002 12:14 pm, Henri Gomez wrote:
> Steve Downey wrote:
> > Actually, with the recent release of commons-logging, we should be able
> > to get rid of the explicit LogKit and Log4J. They're there so as to get a
> > complete build of commons-logging. Tomcat 5 itself doesn't us
Jean-Francois Arcand wrote:
>
>
> Henri Gomez wrote:
>
>> Steve Downey wrote:
>>
>>> Actually, with the recent release of commons-logging, we should be
>>> able to get rid of the explicit LogKit and Log4J. They're there so as
>>> to get a complete build of commons-logging. Tomcat 5 itself doe
Henri Gomez wrote:
> Steve Downey wrote:
>
>> Actually, with the recent release of commons-logging, we should be
>> able to get rid of the explicit LogKit and Log4J. They're there so as
>> to get a complete build of commons-logging. Tomcat 5 itself doesn't
>> use either directly.
>>
>> Xerce
Steve Downey wrote:
> Actually, with the recent release of commons-logging, we should be able to get
> rid of the explicit LogKit and Log4J. They're there so as to get a complete
> build of commons-logging. Tomcat 5 itself doesn't use either directly.
>
> Xerces is a different issue. There was
Actually, with the recent release of commons-logging, we should be able to get
rid of the explicit LogKit and Log4J. They're there so as to get a complete
build of commons-logging. Tomcat 5 itself doesn't use either directly.
Xerces is a different issue. There was a bug that was preventing Tomc
Thank-you, but I still seem to get errors.
Namely the logkit from Avalon is referencing an old verion. I fixed it up
to the following
logkit.home=${base.path}/LogKit-1.1
logkit.lib=${logkit.home}
logkit.jar=${logkit.lib}/logkit-1.1.jar
logkit.loc=http://jakarta.apache.org/builds/jakarta-avalon
You need to be using the HEAD version of digester. It should have been built
in the directory specified by base.path. Double check that it was built
correctly. I just recreated it in my depends directory, and the system built
fine.
A number of the dependencies are unreleased at this point. 'an
Thanks for your answer. That helps quite a bit. Now I have another issue...
build-catalina:
[javac] Compiling 94 source files to
D:\Instructor\Projects\jakarta-tomcat-c
atalina\build\server\classes
[javac]
D:\Instructor\Projects\jakarta-tomcat-catalina\catalina\src\share\or
g\apache
13 matches
Mail list logo
