You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Stefan Bodewig <bo...@apache.org> on 2004/12/15 12:24:03 UTC
Recent Gump Error and DefaultHandler
Hi all,
the last log4j run failed because of
[javac] /home/gump/workspaces2/public/workspace/logging-log4j/src/java/org/apache/log4j/joran/util/JoranDocument.java:126: unreported exception java.io.IOException; must be caught or declared to be thrown
[javac] return super.resolveEntity(publicId, systemId);
[javac] ^
[javac] 1 error
[javac] 5 warnings
and in fact, DefaultHandler throws IOException in JDK 1.5 as well as
the xml-apis.jar produced by xml-commons. The version that ships with
JDK 1.4 does not throw IOException, even though it is listed in the
@throws part of the javadocs (at least in my copy).
I think DefaultHandler has been modified in SAX 2.0.1 to throw the
exception which has always been part of the EntityResolver interface.
Now to this case. Log4J should probably deal with the IOException
case for forwards compatibility reasons, but at the same time adding a
simple throws IOException won't compile on JDK 1.4.
You best bet most probably is to do something like
public InputSource resolveEntity(...) {
...
try {
return super.resolveEntity(publicId, systemId);
} catch (Throwable e) {
if (e instanceof IOException) {
// legal after JDK 1.4, wrap it into a SAXException
throw new SAXExcpetion(e);
} else {
throw e;
}
}
}
Any other ideas?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by Davanum Srinivas <da...@gmail.com>.
Ceki,
see http://brutus.apache.org/...gump runs on 1.4, 1.5 and Kaffe.
-- dims
On Wed, 15 Dec 2004 15:27:09 +0100, Ceki Gülcü <ce...@qos.ch> wrote:
>
> Stefan,
>
> Many thanks for the detailed report and the proposed fix.
>
> If my memory serves me correctly, we have already encountered the same
> exact problem previously and had solved it. This particular instance
> of the problem will get fixed later today.
>
> It's a good thing Gump compiles project with JDK 1.5, instead of JDK
> 1.4 which most of us still seem to use.
>
> On a different but related matter, I would love if Gump's scope
> (or mission statement) could be extended to run tests on the many
> different platforms it is deployed on. If that were the case, Gump
> would act as a virtual test lab, with a huge added value for a project
> like log4j. Gump currently has the technical capability to run test
> cases. So, maybe there is nothing else to change except symbolically
> extend Gump's mission statement.
>
> Perhaps this has been already discussed or is being worked on but
> maybe it is not. I believe the matter deserves some consideration.
>
> At 12:24 PM 12/15/2004, Stefan Bodewig wrote:
> [cut]
>
> >and in fact, DefaultHandler throws IOException in JDK 1.5 as well as
> >the xml-apis.jar produced by xml-commons. The version that ships with
> >JDK 1.4 does not throw IOException, even though it is listed in the
> >@throws part of the javadocs (at least in my copy).
> >
> >Stefan
>
> --
> Ceki Gülcü
>
> The complete log4j manual: http://qos.ch/log4j/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by sebb <se...@gmail.com>.
On Wed, 15 Dec 2004 17:24:53 +0100, Stefan Bodewig <bo...@apache.org> wrote:
> On Wed, 15 Dec 2004, Ceki Gülc <ce...@qos.ch> wrote:
[...]
> > On a different but related matter, I would love if Gump's scope (or
> > mission statement) could be extended to run tests on the many
> > different platforms it is deployed on.
By tests, I assume you mean unit tests and the like?
>
> That is completely in scope of Gump's mission. Right now we run on
[...]
If Gump scope includes running tests, what is the policy on running
tests that require access to servers? I'm thinking of JMeter, but
other packages might also want to test with RMI and http/https/ftp
etc.
S.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 15 Dec 2004, Ceki Gülc <ce...@qos.ch> wrote:
> If my memory serves me correctly, we have already encountered the
> same exact problem previously and had solved it.
Quite possible, one of the nasty little BWC problems of JAXP 1.3.
> This particular instance of the problem will get fixed later today.
Great.
> It's a good thing Gump compiles project with JDK 1.5, instead of JDK
> 1.4 which most of us still seem to use.
It does both - and Kaffe. See <http://brutus.apache.org/>. Right now
Kaffe is getting quite a bit of attention, since we are gradually
adapting Ant and at the same time have the Kaffe peeps implement more
of the Java class lib to get more and more projects to build.
> On a different but related matter, I would love if Gump's scope (or
> mission statement) could be extended to run tests on the many
> different platforms it is deployed on.
That is completely in scope of Gump's mission. Right now we run on
Linux only, but use three different VMs. Personally I'd love to give
ikvm a try one day.
We used to run Gump on nagoya and moof (Solaris and MacOS X
respectively) and may be able to run Gump in VMWare instances on
brutus for more or less arbitrary i386 runnable OSes.
We just need to ensure that it won't become a maintenance nightmare,
which means we have to tweak Gump in several places before that.
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by Stefano Mazzocchi <st...@apache.org>.
Ceki Gülcü wrote:
>
> Stefan,
>
> Many thanks for the detailed report and the proposed fix.
>
> If my memory serves me correctly, we have already encountered the same
> exact problem previously and had solved it. This particular instance
> of the problem will get fixed later today.
>
> It's a good thing Gump compiles project with JDK 1.5, instead of JDK
> 1.4 which most of us still seem to use.
>
> On a different but related matter, I would love if Gump's scope
> (or mission statement) could be extended to run tests on the many
> different platforms it is deployed on. If that were the case, Gump
> would act as a virtual test lab, with a huge added value for a project
> like log4j. Gump currently has the technical capability to run test
> cases. So, maybe there is nothing else to change except symbolically
> extend Gump's mission statement.
>
> Perhaps this has been already discussed or is being worked on but
> maybe it is not. I believe the matter deserves some consideration.
We are in the process of discussing the architecture of Gump 3.0 which
will split gump into three stages:
1) project metadata harvesting (try to capture data from projects
rather than having gump people maintain them)
2) do the build
3) mine and present the build metadata
having the 3 stages separated would allow us to open stage #2 for
multiple machines. The goal is to have as many CPU/OS/Environments as
possible testing our code.
Ceki, as constructors do when they are renovating a space "please,
excuse the mess, we're working to make it better" and we also know that
we cannot simply shut down gump, because if we did, all the uncaught
problems will keep percolating (the tendency of the ecosystem to break
is a *lot* higher than the tendency for the system to heal itself up...
which is something we are concerned about and this new architecture
(with a new social scheme, as you suggested) should make things better).
HTH
--
Stefano.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 15 Dec 2004, Ceki Gülc <ce...@qos.ch> wrote:
> If my memory serves me correctly, we have already encountered the
> same exact problem previously and had solved it.
Quite possible, one of the nasty little BWC problems of JAXP 1.3.
> This particular instance of the problem will get fixed later today.
Great.
> It's a good thing Gump compiles project with JDK 1.5, instead of JDK
> 1.4 which most of us still seem to use.
It does both - and Kaffe. See <http://brutus.apache.org/>. Right now
Kaffe is getting quite a bit of attention, since we are gradually
adapting Ant and at the same time have the Kaffe peeps implement more
of the Java class lib to get more and more projects to build.
> On a different but related matter, I would love if Gump's scope (or
> mission statement) could be extended to run tests on the many
> different platforms it is deployed on.
That is completely in scope of Gump's mission. Right now we run on
Linux only, but use three different VMs. Personally I'd love to give
ikvm a try one day.
We used to run Gump on nagoya and moof (Solaris and MacOS X
respectively) and may be able to run Gump in VMWare instances on
brutus for more or less arbitrary i386 runnable OSes.
We just need to ensure that it won't become a maintenance nightmare,
which means we have to tweak Gump in several places before that.
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by Yoav Shapira <yo...@apache.org>.
Hi,
> On a different but related matter, I would love if Gump's scope
> (or mission statement) could be extended to run tests on the many
Isn't this as simple as changing the "dist" target (which is what Gump runs
IIRC) of the log4j build.xml to include unit tests? Alternatively, and also
IIRC, we can come up with a gump.xml for log4j that does whatever we want,
including unit tests. Gump itself would not need to be modified for this...
But this is all really IIRC, it's been a couple of years since I worked
directly with Gump.
Yoav
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by Ceki Gülcü <ce...@qos.ch>.
Stefan,
Many thanks for the detailed report and the proposed fix.
If my memory serves me correctly, we have already encountered the same
exact problem previously and had solved it. This particular instance
of the problem will get fixed later today.
It's a good thing Gump compiles project with JDK 1.5, instead of JDK
1.4 which most of us still seem to use.
On a different but related matter, I would love if Gump's scope
(or mission statement) could be extended to run tests on the many
different platforms it is deployed on. If that were the case, Gump
would act as a virtual test lab, with a huge added value for a project
like log4j. Gump currently has the technical capability to run test
cases. So, maybe there is nothing else to change except symbolically
extend Gump's mission statement.
Perhaps this has been already discussed or is being worked on but
maybe it is not. I believe the matter deserves some consideration.
At 12:24 PM 12/15/2004, Stefan Bodewig wrote:
[cut]
>and in fact, DefaultHandler throws IOException in JDK 1.5 as well as
>the xml-apis.jar produced by xml-commons. The version that ships with
>JDK 1.4 does not throw IOException, even though it is listed in the
>@throws part of the javadocs (at least in my copy).
>
>Stefan
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Recent Gump Error and DefaultHandler
Posted by Ceki Gülcü <ce...@qos.ch>.
Stefan,
Many thanks for the detailed report and the proposed fix.
If my memory serves me correctly, we have already encountered the same
exact problem previously and had solved it. This particular instance
of the problem will get fixed later today.
It's a good thing Gump compiles project with JDK 1.5, instead of JDK
1.4 which most of us still seem to use.
On a different but related matter, I would love if Gump's scope
(or mission statement) could be extended to run tests on the many
different platforms it is deployed on. If that were the case, Gump
would act as a virtual test lab, with a huge added value for a project
like log4j. Gump currently has the technical capability to run test
cases. So, maybe there is nothing else to change except symbolically
extend Gump's mission statement.
Perhaps this has been already discussed or is being worked on but
maybe it is not. I believe the matter deserves some consideration.
At 12:24 PM 12/15/2004, Stefan Bodewig wrote:
[cut]
>and in fact, DefaultHandler throws IOException in JDK 1.5 as well as
>the xml-apis.jar produced by xml-commons. The version that ships with
>JDK 1.4 does not throw IOException, even though it is listed in the
>@throws part of the javadocs (at least in my copy).
>
>Stefan
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org