Javier padrón wrote:
DEBUG: org.apache.jetspeed.components.jndi.TyrexJNDIComponent - Binding [EMAIL
PROTECTED] to name jdbc/jetspeed
INFO: org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading
XML bean definitions from class path resource [boot/datasource.xml]
[surefire] Tests run: 6, Failures: 0, Errors: 6, Time elapsed: 1.203 sec <<<<<<<< FAILURE !!
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 24 seconds
[INFO] Finished at: Fri Jan 12 10:45:44 GMT 2007
[INFO] Final Memory: 26M/51M
[INFO] ------------------------------------------------------------------------
The stranger is that although the test fails, does deploy and initiates tomcat,
has this something that to see?
Some idea of how solving it?
The tests all passed for me recently on Maven-1 and Maven-2 builds.
It would be great if we had a continuous build setup configured to
verify this on a nightly basis...
If you are new to Jetspeed, we recommend that you do not build from the
source unless you are planning on making changes to the source and
contributing back, or just trying to understand it, as building Jetspeed
requires a good working understanding of either Maven-1 or Maven-2. At
times, it seems that we seem to spend more time supporting the build
than other issues.
Have you tried out our 'standard' integration method for custom builds
described here:
http://portals.apache.org/tutorials/jetspeed-2/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
