logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam R. B. Jack" <aj...@trysybase.com>
Subject Re: Fw: [GUMP@buildnew]: logging-log4j/logging-log4j failed
Date Tue, 08 Jun 2004 13:21:48 GMT
Not quite related to what is said here, but...

>From a Gump perspective,  I really like project separation (which is aided
by ant target and code dependency separation). Personally, I'd like the
chainsaw component out of the main logging (on Gump) project/build, since
folks only depend on (for compilation) the core logging APIs.

Chainsaw is rapidly gaining dependencies (via VFS, etc.) so if we could
create separate Gump projects for logging and logging-chainsaw, then we'd
have far less dependencies on the former. This is good for folks like me,
who run personal (@ work) Gumps on just the core dependencies for my code.
The more optimal the dependency tree, the faster this loop.

regards,

Adam
----- Original Message ----- 
From: "Scott Deboy" <sdeboy@comotivsystems.com>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Sent: Tuesday, June 08, 2004 7:05 AM
Subject: RE: Fw: [GUMP@buildnew]: logging-log4j/logging-log4j failed


My most recent commit (adding an ExpressionRule dependency in
LogFilePatternReceiver) caused this.

I could move this out of core and add it in the Chainsaw target or somewhere
else, I'm fine with it.

I'd like to see support for something like my latest commit in all the
receivers (the ability to filter events as they're being received) based on
a rule, and ExpressionRule seems like a natural fit, but does have the ORO
dependency.  I could nuke the LIKE (regexp) operator but it's pretty useful.

Thoughts?

-----Original Message-----
From: Ceki Gülcü [mailto:ceki@qos.ch]
Sent: Tue 6/8/2004 3:00 AM
To: log4j-dev@logging.apache.org
Cc: Adam R. B. Jack
Subject: Re: Fw: [GUMP@buildnew]: logging-log4j/logging-log4j failed
This is a question for Scott. I think his most recent commits added
this dependency but I am too lazy to check. In any case, looking at
the build.core target in build.xml, the org.apache.log4j.rule package
is part of the core build and apparently it needs ORO.

Scott, should we keep the rule package under build.core target or move
it somewhere else?


At 11:14 PM 6/7/2004, Adam R. B. Jack wrote:
>It seems log4j (and not just log4j-tests) depends upon jakarta-oro. Is this
>intended/permanent?
>
>[I'm doing a CC 'cos Apache mail seems 'slow' today.]
>
>regards,
>
>Adam
>----- Original Message -----
>From: <noreply@qos.ch>
>To: <dev@trysybase.com>
>Sent: Monday, June 07, 2004 8:25 PM
>Subject: [GUMP@buildnew]: logging-log4j/logging-log4j failed
>
>
> > 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 9 projects.
> > Project State : 'Failed', Reason 'Build Failed'
> > The following are affected:
> >     - jakarta-log4j :  Reliable, fast and flexible logging package for
>Java
> >     - jakarta-poi :  POI
> >     - log4j-tests :  Reliable, fast and flexible logging package for
Java
> >     - trysybase :  TrySybase
> >     - trysybase-admin :  TrySybase
> >     - trysybase-extras :  TrySybase Extras
> >     - trysybase-web :  TrySybase Web
> >     - ws-axis :  Apache eXtensible Interaction System
> >     - xml-axis :  Apache eXtensible Interaction System
> >
> >
> > Full details are available at:
> >
> >
>http://buildnew.try.sybase.com/gump/local/logging-log4j/logging-log4j/index
.html
> >
> > That said, some snippets follow:
> >
> >
> > The following annotations were provided:
> >  -WARNING- Bad *Optional* Dependency. Project: jms unknown to *this*
>workspace
> >  -WARNING- Bad *Optional* Dependency. Project: jmx unknown to *this*
>workspace
> >  -INFO- Failed with reason build failed
> >  -INFO- Enable "debug" output, due to build failure.
> >
> >
> > The following work was performed:
> >
>http://buildnew.try.sybase.com/gump/local/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, 10 seconds
> > Command Line:
>java -Xbootclasspath/p:/homelocal/build/gump/local/gump-ws/xml-xerces2/java
/
>build/xercesImpl.jar:/homelocal/build/gump/local/gump-ws/xml-xerces2/java/b
u
>ild/xml-apis.jar
>org.apache.tools.ant.Main -Dgump.merge=/homelocal/build/gump/local/gump/wor
k
>/merge.xml -Djars.dir=/homelocal/build/jars_dir -Ddeployer.username=arb_jac
k
>  -Dbuild.sysclasspath=last -Dforrest.home=/homelocal/build/packages/apache
-f
>orrest-0.4-bin -Dversion=20040607 jar
> > [Working Directory: /homelocal/build/gump/local/gump-ws/logging-log4j]
> > CLASSPATH :
>/usr/java/j2sdk1.4.2_03/lib/tools.jar:/homelocal/build/gump/local/gump-ws/l
o
>gging-log4j/dist/classes:/homelocal/build/gump/local/gump-ws/ant/dist/lib/a
n
>t-stylebook.jar:/homelocal/build/gump/local/gump-ws/ant/dist/lib/ant-jmf.ja
r
>:/homelocal/build/gump/local/gump-ws/ant/dist/lib/ant-swing.jar:/homelocal/
b
>uild/gump/local/gump-ws/ant/dist/lib/ant-junit.jar:/homelocal/build/gump/lo
c
>al/gump-ws/ant/dist/lib/ant-launcher.jar:/homelocal/build/gump/local/gump-w
s
>/ant/dist/lib/ant-trax.jar:/homelocal/build/gump/local/gump-ws/ant/dist/lib
/
>ant.jar:/homelocal/build/gump/local/gump-ws/ant/dist/lib/ant-nodeps.jar:/ho
m
>elocal/build/gump/local/gump-ws/jakarta-servletapi-4/lib/servlet.jar:/homel
o
>cal/build/gump/local/gump-ws/dist/junit/junit.jar:/homelocal/build/gump/pac
k
>ages/javamail-1.3/mail.jar---------------------------------------------
> >     [javac]     Perl5Compiler compiler = new Perl5Compiler();
> >     [javac]                                  ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:63: cannot resolve symbol
> >     [javac] symbol  : class Pattern
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]     Pattern pattern1 = null;
> >     [javac]     ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:66: cannot resolve symbol
> >     [javac] symbol  : variable Perl5Compiler
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]       pattern1 = compiler.compile(pattern,
>Perl5Compiler.CASE_INSENSITIVE_MASK);
> >     [javac]                                            ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:67: cannot resolve symbol
> >     [javac] symbol  : class MalformedPatternException
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]     } catch (MalformedPatternException e) {
> >     [javac]              ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:92: cannot resolve symbol
> >     [javac] symbol  : class Perl5Compiler
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]            Perl5Compiler compiler = new Perl5Compiler();
> >     [javac]            ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:92: cannot resolve symbol
> >     [javac] symbol  : class Perl5Compiler
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]            Perl5Compiler compiler = new Perl5Compiler();
> >     [javac]                                         ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:93: cannot resolve symbol
> >     [javac] symbol  : class Perl5Matcher
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]            matcher = new Perl5Matcher();
> >     [javac]                          ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:94: cannot resolve symbol
> >     [javac] symbol  : variable Perl5Compiler
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]            pattern = compiler.compile(patternString,
>Perl5Compiler.CASE_INSENSITIVE_MASK);
> >     [javac]                                                      ^
> >     [javac]
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>rule/LikeRule.java:95: cannot resolve symbol
> >     [javac] symbol  : class MalformedPatternException
> >     [javac] location: class org.apache.log4j.rule.LikeRule
> >     [javac]          } catch (MalformedPatternException e) {
> >     [javac]                   ^
> >     [javac] Note:
>/homelocal/build/gump/local/gump-ws/logging-log4j/src/java/org/apache/log4j
/
>PropertyConfigurator.java uses or overrides a deprecated API.
> >     [javac] Note: Recompile with -deprecation for details.
> >     [javac] 18 errors
> >
> > BUILD FAILED
> > /homelocal/build/gump/local/gump-ws/logging-log4j/build.xml:242: Compile
>failed; see the compiler error output for details.
> >
> > Total time: 8 seconds
> > ---------------------------------------------
> >
> >
> >
> >
> > To subscribe to this information via syndicated feeds:
> >  RSS:
>http://buildnew.try.sybase.com/gump/local/logging-log4j/logging-log4j/rss.x
ml
> >  Atom:
>http://buildnew.try.sybase.com/gump/local/logging-log4j/logging-log4j/atom.
xml
> >
> >
> > --
> > Produced by Gump 2.0.3-alpha-0002.
> > [Run (20040607 14:00:09, buildnew.try.sybase.com:local:20040607
14:00:09)]
> > http://buildnew.try.sybase.com/gump/local/index.html
> > http://buildnew.try.sybase.com/gump/local/options.html
> >
> > --
> > Apache Gump
> > http://gump.apache.org/ [Instance: buildnew.try.sybase.com]
> >

-- 
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







----------------------------------------------------------------------------
----


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message