You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Ceki Gülcü <ce...@qos.ch> on 2004/05/27 10:22:28 UTC
Re: [GUMP@brutus]: logging-log4j/logging-log4j failed
Hello all,
It appears that log4j is failing to compile on brutus. It compiles
fine on my side using JDK 1.4, 1.3 or 1.2. The problem appears to be
linked to the signature of the resolveEntity() method in
org.xml.sax.helpers.DefaultHandler. Contrary to what is declared by
the resolveEntity method in EntityResolver interface, the
resolveEntity method in the DefaultHandler is not declared as throwing
an IOException. (It masks the IOException.)
Here is the code from the org.apache.joran.Interpreter class which
fails to compile on Brutus.
// Joran builds as part of log4j.
package org.apache.joran;
public class Interpreter extends DefaultHandler {
....
/**
* If a specific entityResolver is set for this Interpreter instance, then
* we use it to resolve entities. Otherwise, we use the default
implementation
* offered by the super class.
*/
public InputSource resolveEntity(String publicId, String systemId)
throws SAXException {
if(entityResolver == null) {
return super.resolveEntity(publicId, systemId);
} else {
try {
return entityResolver.resolveEntity(publicId, systemId);
} catch(IOException ioe) {
// fall back to the default implementation
return super.resolveEntity(publicId, systemId);
}
}
}
}
Which version of the org.xml.sax package is used on brutus? I am a bit
at a loss here.
Thanks in advance for shedding some light on to the matter.
At 10:38 PM 5/26/2004, noreply@qos.ch wrote:
>To whom it may engage...
>
>This is an automated request, but not an unsolicited one. For
>more information please visit http://gump.apache.org/nagged.html,
>and/or contact folk at general@gump.apache.org.
>
>Project logging-log4j has an issue affecting its community integration.
>This issue affects 213 projects.
>Project State : 'Failed', Reason 'Build Failed'
>The following are affected:
> - ant-embed-optional : Java based build tool
> - avalon : Avalon's main repository.
[snip]
>Full details are available at:
>
> http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/index.html
>
>That said, some snippets follow:
>
>
>The following annotations were provided:
> -INFO- Failed with reason build failed
> -INFO- Enable "debug" output, due to build failure.
>
>
>The following work was performed:
>http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/gump_work/build_logging-log4j_logging-log4j.html
>Work Name: build_logging-log4j_logging-log4j (Type: Build)
>State: Failed
>Elapsed: 0 hours, 0 minutes, 4 seconds
>Command Line: java -Djava.awt.headless=true
>-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
>org.apache.tools.ant.Main
>-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
>-Dbuild.sysclasspath=only -Dversion=20040526 jar
>[Working Directory: /usr/local/gump/public/workspace/logging-log4j]
>CLASSPATH :
>/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.0.2/lib/jms.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxtools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/javamail-1.3/mail.jar--------------------------------------
>-------
>Buildfile: build.xml
>
>init:
>
>jndiCheck:
>
>build.core:
> [mkdir] Created dir:
> /usr/local/gump/public/workspace/logging-log4j/dist/classes
> [javac] Compiling 220 source files to
> /usr/local/gump/public/workspace/logging-log4j/dist/classes
> [javac]
> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:301:
> unreported exception java.io.IOException; must be caught or declared to
> be thrown
> [javac] return super.resolveEntity(publicId, systemId);
> [javac] ^
> [javac]
> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:307:
> unreported exception java.io.IOException; must be caught or declared to
> be thrown
> [javac] return super.resolveEntity(publicId, systemId);
> [javac] ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -deprecation for details.
> [javac] 2 errors
>
>BUILD FAILED
>/usr/local/gump/public/workspace/logging-log4j/build.xml:242: Compile
>failed; see the compiler error output for details.
>
>--
>Apache Gump
>http://gump.apache.org/ [Instance: brutus]
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-dev-help@logging.apache.org
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: logging-log4j/logging-log4j failed
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> Which version of the org.xml.sax package is used on brutus? I am a bit
> at a loss here.
The very latest (CVS HEAD) of xerces.
http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/details.html#Boot+Classpath
This issue is seeming vaguely familiar -- I think somebody else hit it
before -- but I'll need some coffee (and to wake up) before I could possibly
bring it back into context. Further, this is similar to a posting I made
about exceptions not being in signatures (two days ago, for [codec]) -- how
do we cope with when they change. The signature doesn't change, but compile
time does. [The ws-xmlrpc over codec case is the reverse, they are catching
an exception that is no longer thrown, hence failing to compile.]
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: logging-log4j/logging-log4j failed
Posted by Ceki Gülcü <ce...@qos.ch>.
The solution to this curious problem was to directly implement the
DefaultHandler.resolveEntity functionality which is simply to return
null. Trying to be OO and calling DefaultHandler.resolveEntity can
quickly develop to become a monstrous headache as the signature of
DefaultHandler.resolveEntity is "variable".
At 10:52 AM 5/27/2004, Ceki Gülcü wrote:
>Problem solved. It appears that the org.xml.sax classes included in
>the JDK differ from those of the original.
>
>Dancing around the discrepancy is not too difficult once you know that
>it exists. Thanks to gump for pointing out the difference.
>
>How inconsiderate on the part of Sun to modify an existing API and
>bundle the modified version with the JDK.
>
>At 10:22 AM 5/27/2004, Ceki Gülcü wrote:
>>Hello all,
>>
>>It appears that log4j is failing to compile on brutus. It compiles
>>fine on my side using JDK 1.4, 1.3 or 1.2. The problem appears to be
>>linked to the signature of the resolveEntity() method in
>>org.xml.sax.helpers.DefaultHandler. Contrary to what is declared by
>>the resolveEntity method in EntityResolver interface, the
>>resolveEntity method in the DefaultHandler is not declared as throwing
>>an IOException. (It masks the IOException.)
>>
>>Here is the code from the org.apache.joran.Interpreter class which
>>fails to compile on Brutus.
>>
>>// Joran builds as part of log4j.
>>package org.apache.joran;
>>
>>public class Interpreter extends DefaultHandler {
>>
>> ....
>>
>> /**
>> * If a specific entityResolver is set for this Interpreter instance, then
>> * we use it to resolve entities. Otherwise, we use the default
>> implementation
>> * offered by the super class.
>> */
>> public InputSource resolveEntity(String publicId, String systemId)
>> throws SAXException {
>> if(entityResolver == null) {
>> return super.resolveEntity(publicId, systemId);
>> } else {
>> try {
>> return entityResolver.resolveEntity(publicId, systemId);
>> } catch(IOException ioe) {
>> // fall back to the default implementation
>> return super.resolveEntity(publicId, systemId);
>> }
>> }
>> }
>>}
>>
>>Which version of the org.xml.sax package is used on brutus? I am a bit
>>at a loss here.
>>
>>Thanks in advance for shedding some light on to the matter.
>>
>>
>>
>>At 10:38 PM 5/26/2004, noreply@qos.ch wrote:
>>>To whom it may engage...
>>>
>>>This is an automated request, but not an unsolicited one. For
>>>more information please visit http://gump.apache.org/nagged.html,
>>>and/or contact folk at general@gump.apache.org.
>>>
>>>Project logging-log4j has an issue affecting its community integration.
>>>This issue affects 213 projects.
>>>Project State : 'Failed', Reason 'Build Failed'
>>>The following are affected:
>>> - ant-embed-optional : Java based build tool
>>> - avalon : Avalon's main repository.
>>
>>[snip]
>>
>>>Full details are available at:
>>>
>>>http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/index.html
>>>
>>>That said, some snippets follow:
>>>
>>>
>>>The following annotations were provided:
>>> -INFO- Failed with reason build failed
>>> -INFO- Enable "debug" output, due to build failure.
>>>
>>>
>>>The following work was performed:
>>>http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/gump_work/build_logging-log4j_logging-log4j.html
>>>Work Name: build_logging-log4j_logging-log4j (Type: Build)
>>>State: Failed
>>>Elapsed: 0 hours, 0 minutes, 4 seconds
>>>Command Line: java -Djava.awt.headless=true
>>>-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
>>>org.apache.tools.ant.Main
>>>-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
>>>-Dbuild.sysclasspath=only -Dversion=20040526 jar
>>>[Working Directory: /usr/local/gump/public/workspace/logging-log4j]
>>>CLASSPATH :
>>>/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.0.2/lib/jms.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxtools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/javamail-1.3/mail.jar--------------------------------------
>>> -------
>>>Buildfile: build.xml
>>>
>>>init:
>>>
>>>jndiCheck:
>>>
>>>build.core:
>>> [mkdir] Created dir:
>>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>>> [javac] Compiling 220 source files to
>>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>>> [javac]
>>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:301:
>>> unreported exception java.io.IOException; must be caught or declared to
>>> be thrown
>>> [javac] return super.resolveEntity(publicId, systemId);
>>> [javac] ^
>>> [javac]
>>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:307:
>>> unreported exception java.io.IOException; must be caught or declared to
>>> be thrown
>>> [javac] return super.resolveEntity(publicId, systemId);
>>> [javac] ^
>>> [javac] Note: Some input files use or override a deprecated API.
>>> [javac] Note: Recompile with -deprecation for details.
>>> [javac] 2 errors
>>>
>>>BUILD FAILED
>>>/usr/local/gump/public/workspace/logging-log4j/build.xml:242: Compile
>>>failed; see the compiler error output for details.
>>>
>>>--
>>>Apache Gump
>>>http://gump.apache.org/ [Instance: brutus]
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>>For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>--
>>Ceki Gülcü
>>
>> For log4j documentation consider "The complete log4j manual"
>> ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
>>For additional commands, e-mail: general-help@gump.apache.org
>
>--
>Ceki Gülcü
>
> For log4j documentation consider "The complete log4j manual"
> ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
>For additional commands, e-mail: general-help@gump.apache.org
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
blog this was: [GUMP@brutus]: logging-log4j/logging-log4j failed
Posted by Nick Chalko <ni...@chalko.com>.
We need to blog this on peas and carrots after the long vacation.
Ceki Gülcü wrote:
> Problem solved. It appears that the org.xml.sax classes included in
> the JDK differ from those of the original.
>
> Dancing around the discrepancy is not too difficult once you know that
> it exists. Thanks to gump for pointing out the difference.
>
> How inconsiderate on the part of Sun to modify an existing API and
> bundle the modified version with the JDK.
>
> At 10:22 AM 5/27/2004, Ceki Gülcü wrote:
>
>> Hello all,
>>
>> It appears that log4j is failing to compile on brutus. It compiles
>> fine on my side using JDK 1.4, 1.3 or 1.2. The problem appears to be
>> linked to the signature of the resolveEntity() method in
>> org.xml.sax.helpers.DefaultHandler. Contrary to what is declared by
>> the resolveEntity method in EntityResolver interface, the
>> resolveEntity method in the DefaultHandler is not declared as throwing
>> an IOException. (It masks the IOException.)
>>
>> Here is the code from the org.apache.joran.Interpreter class which
>> fails to compile on Brutus.
>>
>> // Joran builds as part of log4j.
>> package org.apache.joran;
>>
>> public class Interpreter extends DefaultHandler {
>>
>> ....
>>
>> /**
>> * If a specific entityResolver is set for this Interpreter
>> instance, then
>> * we use it to resolve entities. Otherwise, we use the default
>> implementation
>> * offered by the super class.
>> */
>> public InputSource resolveEntity(String publicId, String systemId)
>> throws SAXException {
>> if(entityResolver == null) {
>> return super.resolveEntity(publicId, systemId);
>> } else {
>> try {
>> return entityResolver.resolveEntity(publicId, systemId);
>> } catch(IOException ioe) {
>> // fall back to the default implementation
>> return super.resolveEntity(publicId, systemId);
>> }
>> }
>> }
>> }
>>
>> Which version of the org.xml.sax package is used on brutus? I am a bit
>> at a loss here.
>>
>> Thanks in advance for shedding some light on to the matter.
>>
>>
>>
>> At 10:38 PM 5/26/2004, noreply@qos.ch wrote:
>>
>>> To whom it may engage...
>>>
>>> This is an automated request, but not an unsolicited one. For
>>> more information please visit http://gump.apache.org/nagged.html,
>>> and/or contact folk at general@gump.apache.org.
>>>
>>> Project logging-log4j has an issue affecting its community integration.
>>> This issue affects 213 projects.
>>> Project State : 'Failed', Reason 'Build Failed'
>>> The following are affected:
>>> - ant-embed-optional : Java based build tool
>>> - avalon : Avalon's main repository.
>>
>>
>> [snip]
>>
>>> Full details are available at:
>>>
>>>
>>> http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/index.html
>>>
>>>
>>> That said, some snippets follow:
>>>
>>>
>>> The following annotations were provided:
>>> -INFO- Failed with reason build failed
>>> -INFO- Enable "debug" output, due to build failure.
>>>
>>>
>>> The following work was performed:
>>> http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/gump_work/build_logging-log4j_logging-log4j.html
>>>
>>> Work Name: build_logging-log4j_logging-log4j (Type: Build)
>>> State: Failed
>>> Elapsed: 0 hours, 0 minutes, 4 seconds
>>> Command Line: java -Djava.awt.headless=true
>>> -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
>>> org.apache.tools.ant.Main
>>> -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
>>> -Dbuild.sysclasspath=only -Dversion=20040526 jar
>>> [Working Directory: /usr/local/gump/public/workspace/logging-log4j]
>>> CLASSPATH :
>>> /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.0.2/lib/jms.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxtools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/javamail-1.3/mail.jar--------------------------------------
>>> -------
>>> Buildfile: build.xml
>>>
>>> init:
>>>
>>> jndiCheck:
>>>
>>> build.core:
>>> [mkdir] Created dir:
>>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>>> [javac] Compiling 220 source files to
>>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>>> [javac]
>>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:301:
>>> unreported exception java.io.IOException; must be caught or declared
>>> to be thrown
>>> [javac] return super.resolveEntity(publicId, systemId);
>>> [javac] ^
>>> [javac]
>>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:307:
>>> unreported exception java.io.IOException; must be caught or declared
>>> to be thrown
>>> [javac] return super.resolveEntity(publicId, systemId);
>>> [javac] ^
>>> [javac] Note: Some input files use or override a deprecated API.
>>> [javac] Note: Recompile with -deprecation for details.
>>> [javac] 2 errors
>>>
>>> BUILD FAILED
>>> /usr/local/gump/public/workspace/logging-log4j/build.xml:242:
>>> Compile failed; see the compiler error output for details.
>>>
>>> --
>>> Apache Gump
>>> http://gump.apache.org/ [Instance: brutus]
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
>> --
>> Ceki Gülcü
>>
>> For log4j documentation consider "The complete log4j manual"
>> ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
>> For additional commands, e-mail: general-help@gump.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: logging-log4j/logging-log4j failed
Posted by Ceki Gülcü <ce...@qos.ch>.
At 10:54 AM 5/27/2004, Paul Smith wrote:
>On Thu, 27 May 2004, Ceki [iso-8859-1] Gülcü wrote:
>
> > Problem solved. It appears that the org.xml.sax classes included in
> > the JDK differ from those of the original.
> >
> > Dancing around the discrepancy is not too difficult once you know that
> > it exists. Thanks to gump for pointing out the difference.
> >
> > How inconsiderate on the part of Sun to modify an existing API and
> > bundle the modified version with the JDK.
> >
>
>Now if only they would modify the Date/Calendar API... I would have no
>problem with that.... at all....
I'd like Sun to remove the Thread.interrupt method, i.e. the
quintessential anti-pattern in its sheer evil form. It does not work
as expected and makes robust concurrent code so much harder, some
would say impossible, to write.
>Paul
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [GUMP@brutus]: logging-log4j/logging-log4j failed
Posted by Paul Smith <ps...@apache.org>.
On Thu, 27 May 2004, Ceki [iso-8859-1] Gülcü wrote:
> Problem solved. It appears that the org.xml.sax classes included in
> the JDK differ from those of the original.
>
> Dancing around the discrepancy is not too difficult once you know that
> it exists. Thanks to gump for pointing out the difference.
>
> How inconsiderate on the part of Sun to modify an existing API and
> bundle the modified version with the JDK.
>
Now if only they would modify the Date/Calendar API... I would have no
problem with that.... at all....
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [GUMP@brutus]: logging-log4j/logging-log4j failed
Posted by Ceki Gülcü <ce...@qos.ch>.
Problem solved. It appears that the org.xml.sax classes included in
the JDK differ from those of the original.
Dancing around the discrepancy is not too difficult once you know that
it exists. Thanks to gump for pointing out the difference.
How inconsiderate on the part of Sun to modify an existing API and
bundle the modified version with the JDK.
At 10:22 AM 5/27/2004, Ceki Gülcü wrote:
>Hello all,
>
>It appears that log4j is failing to compile on brutus. It compiles
>fine on my side using JDK 1.4, 1.3 or 1.2. The problem appears to be
>linked to the signature of the resolveEntity() method in
>org.xml.sax.helpers.DefaultHandler. Contrary to what is declared by
>the resolveEntity method in EntityResolver interface, the
>resolveEntity method in the DefaultHandler is not declared as throwing
>an IOException. (It masks the IOException.)
>
>Here is the code from the org.apache.joran.Interpreter class which
>fails to compile on Brutus.
>
>// Joran builds as part of log4j.
>package org.apache.joran;
>
>public class Interpreter extends DefaultHandler {
>
> ....
>
> /**
> * If a specific entityResolver is set for this Interpreter instance, then
> * we use it to resolve entities. Otherwise, we use the default
> implementation
> * offered by the super class.
> */
> public InputSource resolveEntity(String publicId, String systemId)
> throws SAXException {
> if(entityResolver == null) {
> return super.resolveEntity(publicId, systemId);
> } else {
> try {
> return entityResolver.resolveEntity(publicId, systemId);
> } catch(IOException ioe) {
> // fall back to the default implementation
> return super.resolveEntity(publicId, systemId);
> }
> }
> }
>}
>
>Which version of the org.xml.sax package is used on brutus? I am a bit
>at a loss here.
>
>Thanks in advance for shedding some light on to the matter.
>
>
>
>At 10:38 PM 5/26/2004, noreply@qos.ch wrote:
>>To whom it may engage...
>>
>>This is an automated request, but not an unsolicited one. For
>>more information please visit http://gump.apache.org/nagged.html,
>>and/or contact folk at general@gump.apache.org.
>>
>>Project logging-log4j has an issue affecting its community integration.
>>This issue affects 213 projects.
>>Project State : 'Failed', Reason 'Build Failed'
>>The following are affected:
>> - ant-embed-optional : Java based build tool
>> - avalon : Avalon's main repository.
>
>[snip]
>
>>Full details are available at:
>>
>>
>>http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/index.html
>>
>>That said, some snippets follow:
>>
>>
>>The following annotations were provided:
>> -INFO- Failed with reason build failed
>> -INFO- Enable "debug" output, due to build failure.
>>
>>
>>The following work was performed:
>>http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/gump_work/build_logging-log4j_logging-log4j.html
>>Work Name: build_logging-log4j_logging-log4j (Type: Build)
>>State: Failed
>>Elapsed: 0 hours, 0 minutes, 4 seconds
>>Command Line: java -Djava.awt.headless=true
>>-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
>>org.apache.tools.ant.Main
>>-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
>>-Dbuild.sysclasspath=only -Dversion=20040526 jar
>>[Working Directory: /usr/local/gump/public/workspace/logging-log4j]
>>CLASSPATH :
>>/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.0.2/lib/jms.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxtools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/javamail-1.3/mail.jar--------------------------------------
>> -------
>>Buildfile: build.xml
>>
>>init:
>>
>>jndiCheck:
>>
>>build.core:
>> [mkdir] Created dir:
>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>> [javac] Compiling 220 source files to
>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>> [javac]
>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:301:
>> unreported exception java.io.IOException; must be caught or declared to
>> be thrown
>> [javac] return super.resolveEntity(publicId, systemId);
>> [javac] ^
>> [javac]
>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:307:
>> unreported exception java.io.IOException; must be caught or declared to
>> be thrown
>> [javac] return super.resolveEntity(publicId, systemId);
>> [javac] ^
>> [javac] Note: Some input files use or override a deprecated API.
>> [javac] Note: Recompile with -deprecation for details.
>> [javac] 2 errors
>>
>>BUILD FAILED
>>/usr/local/gump/public/workspace/logging-log4j/build.xml:242: Compile
>>failed; see the compiler error output for details.
>>
>>--
>>Apache Gump
>>http://gump.apache.org/ [Instance: brutus]
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>--
>Ceki Gülcü
>
> For log4j documentation consider "The complete log4j manual"
> ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
>For additional commands, e-mail: general-help@gump.apache.org
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP@brutus]: logging-log4j/logging-log4j failed
Posted by Ceki Gülcü <ce...@qos.ch>.
Problem solved. It appears that the org.xml.sax classes included in
the JDK differ from those of the original.
Dancing around the discrepancy is not too difficult once you know that
it exists. Thanks to gump for pointing out the difference.
How inconsiderate on the part of Sun to modify an existing API and
bundle the modified version with the JDK.
At 10:22 AM 5/27/2004, Ceki Gülcü wrote:
>Hello all,
>
>It appears that log4j is failing to compile on brutus. It compiles
>fine on my side using JDK 1.4, 1.3 or 1.2. The problem appears to be
>linked to the signature of the resolveEntity() method in
>org.xml.sax.helpers.DefaultHandler. Contrary to what is declared by
>the resolveEntity method in EntityResolver interface, the
>resolveEntity method in the DefaultHandler is not declared as throwing
>an IOException. (It masks the IOException.)
>
>Here is the code from the org.apache.joran.Interpreter class which
>fails to compile on Brutus.
>
>// Joran builds as part of log4j.
>package org.apache.joran;
>
>public class Interpreter extends DefaultHandler {
>
> ....
>
> /**
> * If a specific entityResolver is set for this Interpreter instance, then
> * we use it to resolve entities. Otherwise, we use the default
> implementation
> * offered by the super class.
> */
> public InputSource resolveEntity(String publicId, String systemId)
> throws SAXException {
> if(entityResolver == null) {
> return super.resolveEntity(publicId, systemId);
> } else {
> try {
> return entityResolver.resolveEntity(publicId, systemId);
> } catch(IOException ioe) {
> // fall back to the default implementation
> return super.resolveEntity(publicId, systemId);
> }
> }
> }
>}
>
>Which version of the org.xml.sax package is used on brutus? I am a bit
>at a loss here.
>
>Thanks in advance for shedding some light on to the matter.
>
>
>
>At 10:38 PM 5/26/2004, noreply@qos.ch wrote:
>>To whom it may engage...
>>
>>This is an automated request, but not an unsolicited one. For
>>more information please visit http://gump.apache.org/nagged.html,
>>and/or contact folk at general@gump.apache.org.
>>
>>Project logging-log4j has an issue affecting its community integration.
>>This issue affects 213 projects.
>>Project State : 'Failed', Reason 'Build Failed'
>>The following are affected:
>> - ant-embed-optional : Java based build tool
>> - avalon : Avalon's main repository.
>
>[snip]
>
>>Full details are available at:
>>
>>
>>http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/index.html
>>
>>That said, some snippets follow:
>>
>>
>>The following annotations were provided:
>> -INFO- Failed with reason build failed
>> -INFO- Enable "debug" output, due to build failure.
>>
>>
>>The following work was performed:
>>http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/gump_work/build_logging-log4j_logging-log4j.html
>>Work Name: build_logging-log4j_logging-log4j (Type: Build)
>>State: Failed
>>Elapsed: 0 hours, 0 minutes, 4 seconds
>>Command Line: java -Djava.awt.headless=true
>>-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
>>org.apache.tools.ant.Main
>>-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
>>-Dbuild.sysclasspath=only -Dversion=20040526 jar
>>[Working Directory: /usr/local/gump/public/workspace/logging-log4j]
>>CLASSPATH :
>>/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-xalan2.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.0.2/lib/jms.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxtools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/javamail-1.3/mail.jar--------------------------------------
>> -------
>>Buildfile: build.xml
>>
>>init:
>>
>>jndiCheck:
>>
>>build.core:
>> [mkdir] Created dir:
>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>> [javac] Compiling 220 source files to
>> /usr/local/gump/public/workspace/logging-log4j/dist/classes
>> [javac]
>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:301:
>> unreported exception java.io.IOException; must be caught or declared to
>> be thrown
>> [javac] return super.resolveEntity(publicId, systemId);
>> [javac] ^
>> [javac]
>> /usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:307:
>> unreported exception java.io.IOException; must be caught or declared to
>> be thrown
>> [javac] return super.resolveEntity(publicId, systemId);
>> [javac] ^
>> [javac] Note: Some input files use or override a deprecated API.
>> [javac] Note: Recompile with -deprecation for details.
>> [javac] 2 errors
>>
>>BUILD FAILED
>>/usr/local/gump/public/workspace/logging-log4j/build.xml:242: Compile
>>failed; see the compiler error output for details.
>>
>>--
>>Apache Gump
>>http://gump.apache.org/ [Instance: brutus]
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>--
>Ceki Gülcü
>
> For log4j documentation consider "The complete log4j manual"
> ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
>For additional commands, e-mail: general-help@gump.apache.org
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org