Hi Eric,

+) actually it is not a YAAFI container problem - it is a problem in the
glue code between Turbine and YAAFI to map a Commons Logger to an Avalon
Logger. The good news are that the Avalon library seems to provide an
CommonsLogger now which shoud solve the problem nicely.

+) if we are moving towards a release we should not depend on an
unreleased commons-logging and log4j.

Cheers,

Siegfried Goeschl

Eric Pugh wrote:
What do you'all think about just depending on commons-logging-1.1- dev?
That would get us around this compile issue. , can we change how
Yaafi works so that we don't go down to the implementation level of the
commons-logging?

Eric
Dec 4, 2005, at 7:37 AM, turbine-dev (AT) jakarta (DOT) apache.org wrote:

>To whom it may engage
>>
>This is an automated request, but not an unsolicited one. For
>more information please visit ,
>and/or contact the folk at general (AT) gump (DOT) apache.org.
>>
>Project jakarta-turbine-2 has an issue affecting its community
>integration.
>This issue affects 2 projects,
>and has been outstanding for 4 runs.
>The current state of this project is 'Failed', with reason 'Build
>Failed'.
>For reference only, the following projects are affected by this:
>- : Services Framework
>- jakarta-turbine-2 : A servlet based framework.
>>
>>
>Full details are available at:
>
>turbine-2/index.html
>>
>That said, some information snippets are provided here.
>>
>The following annotations (
>messages) were provided:
>-DEBUG- Sole output [turbine-04122005.jar] identifier set to project
>name
>-DEBUG- Dependency on excalibur-logkit exists, no need to add for
>property maven.jar.logkit.
>-DEBUG- Dependency on excalibur-pool-api exists, no need to add for
>property maven.jar.excalibur-pool.
>-DEBUG- Dependency on excalibur-instrument-api exists, no need to
>add for property
>-DEBUG- Dependency on excalibur-framework-api exists, no need to add
>for property
>-DEBUG- Dependency on excalibur-framework-impl exists, no need to
>add for property
>-INF Made directory [/
>turbine-2/target]
>-WARNING- Maven properties: [/usr/local/gump/public/
>]
>-DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/
>
>-INF Failed with reason build failed
>-DEBUG- Maven PM in: /
>turbine-2/project.xml
>-DEBUG- Maven project properties in: /usr/local/gump/public/
>
>-INF Failed to extract fallback artifacts from Gump Repository
>>
>>
>>
>The following work was performed:
>
>
>Work Name: (Type: Build)
>Work ended in a state of : Failed
>Elapsed: 11 secs
>Command Line: maven jar
>[Working Directory: / turbine-2]
>CLASSPATH: /
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>__ __
>| \/ |__ _Apache__
>| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>|_| |_\__,_|\_/\|_||_| v. 1.0.2
>>
>Tag library requested that is not present: 'maven' in plugin: 'null'
>build:start:
>>
>java:prepare-filesystem:
>[mkdir] Created dir: /
>turbine-2/target/classes
>>
>java:compile:
>[echo] Compiling to /
>target/classes
>[echo]
>
>>
>NTE: Targetting JVM 1.4, classes
>will not run on earlier JVMs
>>
>
>>
>[javac] Compiling 347 source files to /x1/gump/public/workspace/
>
>/
>
>270: cannot resolve symbol
>symbol : class Log4JLogger
>location: package impl
>if( log instanceof )
>^
>/
>
>274: cannot resolve symbol
>symbol : class Log4JLogger
>location: package impl
>(()
>log).getLogger()
>^
>Note: Some input files use or override a deprecated API.
>Note: Recompile with -deprecation for details.
>2 errors
>>
>BUILD FAILED
>File /
>Element ant:javac
>Line 63
>Column 48
>Compile failed; see the compiler error output for details.
>Total time: 11 seconds
>Finished at: Sun Dec 04 04:37:33 PST 2005
>>
>
>>
>To subscribe to this information via syndicated feeds:
>- RSS:
>jakarta-turbine-2/rss.xml
>- Atom:
>jakarta-turbine-2/atom.xml
>>
>Gump Tracking
>Produced by Gump version 2.2.
>Gump Run 21000004122005, 21000004122005
>Gump E-mail Identifier (unique within run) #41.
>>
>--
>Apache Gump
>http://gump.apache.org/ [Instance: vmgump]
>>
>
>To unsubscribe, e-mail: turbine-dev-unsubscribe (AT) jakarta (DOT) apache.org
>For additional commands, e-mail: turbine-dev-help (AT) jakarta (DOT) apache.org
>>

To unsubscribe, e-mail: turbine-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: turbine-dev-help (AT) jakarta (DOT) apache.org

To unsubscribe, e-mail: turbine-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: turbine-dev-help (AT) jakarta (DOT) apache.org

Yes, you are right! I think I got all wrapped up in trying to get
Gump to do a clean build of Turbine. Can't wait to see what
CommonsLogger does!

ERic

Dec 5, 2005, at 4:35 AM, Siegfried Goeschl wrote:

Hi Eric,

+) actually it is not a YAAFI container problem - it is a problem
in the glue code between Turbine and YAAFI to map a Commons Logger
to an Avalon Logger. The good news are that the Avalon library
seems to provide an CommonsLogger now which shoud solve the problem
nicely.

+) if we are moving towards a release we should not depend on an
unreleased commons-logging and log4j.

Cheers,

Siegfried Goeschl
--
Eric Pugh wrote:
>What do you'all think about just depending on commons-logging-1.1-
>dev? That would get us around this compile issue. , can we
>change how Yaafi works so that we don't go down to the
>implementation level of the commons-logging?
>Eric
>Dec 4, 2005, at 7:37 AM, turbine-dev (AT) jakarta (DOT) apache.org wrote:
To whom it may engage

This is an automated request, but not an unsolicited one. For
more information please visit ,
and/or contact the folk at general (AT) gump (DOT) apache.org.

Project jakarta-turbine-2 has an issue affecting its community
integration.
This issue affects 2 projects,
and has been outstanding for 4 runs.
The current state of this project is 'Failed', with reason
'Build Failed'.
For reference only, the following projects are affected by this:
- : Services Framework
- jakarta-turbine-2 : A servlet based framework.

Full details are available at:

jakarta- turbine-2/index.html

That said, some information snippets are provided here.

The following annotations (
messages) were provided:
-DEBUG- Sole output [turbine-04122005.jar] identifier set to
project name
-DEBUG- Dependency on excalibur-logkit exists, no need to add
for property maven.jar.logkit.
-DEBUG- Dependency on excalibur-pool-api exists, no need to add
for property maven.jar.excalibur-pool.
-DEBUG- Dependency on excalibur-instrument-api exists, no need
to add for property
-DEBUG- Dependency on excalibur-framework-api exists, no need
to add for property
-DEBUG- Dependency on excalibur-framework-impl exists, no need
to add for property
-INF Made directory [/
turbine-2/target]
-WARNING- Maven properties: [/usr/local/gump/public/
]
-DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/

-INF Failed with reason build failed
-DEBUG- Maven PM in: /
turbine-2/project.xml
-DEBUG- Maven project properties in: /usr/local/gump/public/

-INF Failed to extract fallback artifacts from Gump Repository

The following work was performed:

Work Name: (Type: Build)
Work ended in a state of : Failed
Elapsed: 11 secs
Command Line: maven jar
[Working Directory: /
turbine-2]
CLASSPATH: /

public/
workspace/
workspace/ant/
public/workspace/
public/workspace/ant/dist/
launcher.jar:/usr/local/gump/
nodeps.jar:/usr/local/gump/
usr/local/gump/public/
target/excalibur-
workspace/jakarta-
core.jar:/usr/local/
dist/commons-
jakarta-
usr/
target/

usr/
commons-
jakarta-commons/ fileupload/target/commons-
public/workspace/jakarta-

lang/dist/commons-
workspace/jakarta-
commons/logging/dist/commons-
gump/public/workspace/jakarta- commons/logging/dist/commons-
gump/public/workspace/
usr/local/gump/
usr/local/gump/
gump/public/
excalibur-

local/
target/
workspace/
thread-
turbine-
local/gump/
target/fulcrum-
workspace/jakarta-
factory-04122005.jar:/usr/
turbine-fulcrum/pool/target/
gump/public/workspace/jakarta- turbine-fulcrum/intake/target/
local/gump/public/workspace/
target/fulcrum-
workspace/

target/
workspace/
yaafi-04122005.jar:/
httpunit.jar:/usr/
usr/local/gump/public/
public/workspace/jakarta-oro/
gump/public/workspace/
jakarta-regexp/build/jakarta-
public/workspace/jakarta-
gump/public/workspace/ jakarta-velocity/bin/
workspace/jakarta-
gump/packages/
javamail-1.3.2/
jdbc2_0-
usr/

public/
workspace/
packages/
gump/packages/
local/gump/
jdk1.4-0.09.jar:/usr/
mockobjects-alt-jdk1.4-
mockobjects-0.09/
gump/public/
gump/public/
gump/public/
gump/public/
gump/public/
public/
workspace/
workspace/
public/workspace/
gump/public/
local/gump/public/

__ __
| \/ |__ _Apache__
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\|_||_| v. 1.0.2

Tag library requested that is not present: 'maven' in plugin: 'null'
build:start:

java:prepare-filesystem:
[mkdir] Created dir: /
turbine-2/target/classes

java:compile:
[echo] Compiling to /
turbine-2/ target/classes
[echo]

NTE: Targetting JVM 1.4, classes
will not run on earlier JVMs

[javac] Compiling 347 source files to /x1/gump/public/
workspace/
/

270: cannot resolve symbol
symbol : class Log4JLogger
location: package impl
if( log instanceof
)
^
/

274: cannot resolve symbol
symbol : class Log4JLogger
location: package impl
(()
log).getLogger()
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -deprecation for details.
2 errors

BUILD FAILED
File /
plugin.jelly
Element ant:javac
Line 63
Column 48
Compile failed; see the compiler error output for details.
Total time: 11 seconds
Finished at: Sun Dec 04 04:37:33 PST 2005

To subscribe to this information via syndicated feeds:
- RSS:
jakarta-turbine-2/rss.xml
- Atom:
jakarta-turbine-2/atom.xml

Gump Tracking
Produced by Gump version 2.2.
Gump Run 21000004122005,
21000004122005
Gump E-mail Identifier (unique within run) #41.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: turbine-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: turbine-dev-help (AT) jakarta (DOT) apache.org

>
>To unsubscribe, e-mail: turbine-dev-unsubscribe (AT) jakarta (DOT) apache.org
>For additional commands, e-mail: turbine-dev-help (AT) jakarta (DOT) apache.org
>

To unsubscribe, e-mail: turbine-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: turbine-dev-help (AT) jakarta (DOT) apache.org

To unsubscribe, e-mail: turbine-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: turbine-dev-help (AT) jakarta (DOT) apache.org