Currently if you run "maven jar" in the fortress/bean project, the build
runs
to completion, but the output to the console stops right after the test
is run.

If I remove the FortressBeanTestCase.java and rerun the build then
everything
works correctly.

These are the last few lines of my console output:

---
test:compile:

test:test:
[junit] Running org.apache.avalon.fortress.tools.FortressBeanTestCase
WARN 2004-07-30 17:01:10.307 [fortress.system.roles.de] (): Unable to
load class org.apache.avalon.excalibur.datasource.JdbcDataSource. Skipping.
WARN 2004-07-30 17:01:10.327 [fortress.system.roles.de] (): Unable to
load class org.apache.avalon.excalibur.datasource.J2eeDataSource. Skipping.
WARN 2004-07-30 17:01:10.337 [fortress.system.roles.de] (): Unable to
load class org.apache.avalon.excalibur.datasource.InformixDataSource.
Skipping.
WARN 2004-07-30 17:01:10.337 [fortress.system.roles.de] (): Unable to
load class org.apache.avalon.excalibur.monitor.ActiveMonitor. Skipping.
WARN 2004-07-30 17:01:10.347 [fortress.system.roles.de] (): Unable to
load class org.apache.avalon.excalibur.monitor.PassiveMonitor. Skipping.
[INFO] AvalonLogger not found, commons logging not redirected
---

The same thing happens when running the full build. Everything appears to
work correctly but the test is just causing the console output to be
suppressed.
The problem with this is that it will hide the cause of any problems
encountered
later in the build.

Any idea what is going on here?

Cheers,
Leif

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache Excalibur Project -- URL: http://excalibur.apache.org/

Reply via email to