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/03/31 14:35:14 UTC
Re: [GUMP@lsd]: logging-log4j/logging-log4j failed
Hello folks,
We have just received this very recent log4j failure. It is due to a new
dependency on the servlet-api i.e. servlet-api.jar. What should/can we do
to fix this?
Thanks in advance for your help,
At 03:22 AM 3/31/2004 +0000, ceki@apache.org wrote:
>To whom it may engage...
>
>This is an automated request, but not an unsolicited one. For help
>understanding the request please visit
>http://gump.apache.org/nagged.html,
>and/or contact general@gump.apache.org.
>
>Project logging-log4j has an issue affecting its community integration.
>This issue affects 1099 projects. The current state is 'Failed', for
>reason 'Build Failed'
>
>Full details are available at:
>http://lsd.student.utwente.nl/gump/logging-log4j/logging-log4j.html,
>however some snippets follow:
>
>- - - - - -- -- ------------------------------------ G U M P
>
>Gump provided these annotations:
>
> - Error - Failed with reason build failed
> - Info - Enable "debug" output, due to build failure.
>
>
>- - - - - -- -- ------------------------------------ G U M P
>Gump performed this work:
>
>Work Name: build_logging-log4j_logging-log4j (Type: Build)
>State: Failed
>Elapsed: 0 hours, 0 minutes, 9 seconds
>Command Line: java
>-Xbootclasspath/p:/data3/gump/xml-xerces2/java/build/xercesImpl.jar:/data3/gump/xml-xerces2/java/build/xml-apis.jar
>org.apache.tools.ant.Main
>-Dgump.merge=/data3/gump/gump-install/work/merge.xml
>-Dbuild.sysclasspath=only -Dversion=20040331 jar
>[Working Directory: /data3/gump/logging-log4j]
>---------------------------------------------
>Buildfile: build.xml
> [property] dropping /data3/gump/logging-log4j/dist/classes from path as
> it doesn't exist
>
>init:
>
>build.core:
> [mkdir] Created dir: /data3/gump/logging-log4j/dist/classes
> [javac] Compiling 211 source files to
> /data3/gump/logging-log4j/dist/classes
> [javac]
> /data3/gump/logging-log4j/src/java/org/apache/log4j/selector/servlet/ContextDetachingSCL.java:29:
> package javax.servlet does not exist
> [javac] import javax.servlet.ServletContext;
> [javac] ^
> [javac]
> /data3/gump/logging-log4j/src/java/org/apache/log4j/selector/servlet/ContextDetachingSCL.java:30:
> package javax.servlet does not exist
> [javac] import javax.servlet.ServletContextEvent;
> [javac] ^
> [javac]
> /data3/gump/logging-log4j/src/java/org/apache/log4j/selector/servlet/ContextDetachingSCL.java:31:
> package javax.servlet does not exist
> [javac] import javax.servlet.ServletContextListener;
> [javac] ^
> [javac]
> /data3/gump/logging-log4j/src/java/org/apache/log4j/selector/servlet/ContextDetachingSCL.java:46:
> cannot resolve symbol
> [javac] symbol : class ServletContextListener
> [javac] location: class
> org.apache.log4j.selector.servlet.ContextDetachingSCL
> [javac] public class ContextDetachingSCL implements
> ServletContextListener {
> [javac] ^
> [javac]
> /data3/gump/logging-log4j/src/java/org/apache/log4j/selector/servlet/ContextDetachingSCL.java:55:
> cannot resolve symbol
> [javac] symbol : class ServletContextEvent
> [javac] location: class
> org.apache.log4j.selector.servlet.ContextDetachingSCL
> [javac] public void contextDestroyed(ServletContextEvent sce) {
> [javac] ^
> [javac]
> /data3/gump/logging-log4j/src/java/org/apache/log4j/selector/servlet/ContextDetachingSCL.java:83:
> cannot resolve symbol
> [javac] symbol : class ServletContextEvent
> [javac] location: class
> org.apache.log4j.selector.servlet.ContextDetachingSCL
> [javac] public void contextInitialized(ServletContextEvent sce) {
> [javac] ^
> [javac]
> /data3/gump/logging-log4j/src/java/org/apache/log4j/selector/servlet/ContextDetachingSCL.java:84:
> cannot resolve symbol
> [javac] symbol : class ServletContext
> [javac] location: class
> org.apache.log4j.selector.servlet.ContextDetachingSCL
> [javac] ServletContext sc = sce.getServletContext();
> [javac] ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -deprecation for details.
> [javac] 7 errors
>
>BUILD FAILED
>/data3/gump/logging-log4j/build.xml:214: Compile failed; see the compiler
>error output for details.
>
>Total time: 7 seconds
>---------------------------------------------
>
>
>
>
>To subscribe to this information via syndicated feeds:
>RSS: http://lsd.student.utwente.nl/gump/logging-log4j/logging-log4j.rss |
>Atom: http://lsd.student.utwente.nl/gump/logging-log4j/logging-log4j.atom
>
>--
>Gump http://gump.apache.org/
>[lsd]
--
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@lsd]: logging-log4j/logging-log4j failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 31 Mar 2004, Ceki Gülc <ce...@qos.ch> wrote:
> We have just received this very recent log4j failure. It is due to a
> new dependency on the servlet-api i.e. servlet-api.jar. What
> should/can we do to fix this?
The ideal workflow would see you add
<depend project="jakarta-servletapi-4"/>
to your Gump project descriptor. As always, all Apache committers are
Gump committers and you can patch the descriptor yourself, if you find
it, that is 8-)
I've already changed it a few hours ago, so next night's run should be
OK.
Cheers
Stefan
--
http://stefanbodewig.blogger.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [GUMP@lsd]: logging-log4j/logging-log4j failed
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 31 Mar 2004, Ceki Gülc <ce...@qos.ch> wrote:
> We have just received this very recent log4j failure. It is due to a
> new dependency on the servlet-api i.e. servlet-api.jar. What
> should/can we do to fix this?
The ideal workflow would see you add
<depend project="jakarta-servletapi-4"/>
to your Gump project descriptor. As always, all Apache committers are
Gump committers and you can patch the descriptor yourself, if you find
it, that is 8-)
I've already changed it a few hours ago, so next night's run should be
OK.
Cheers
Stefan
--
http://stefanbodewig.blogger.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org