Hi General Gump,
On 23.08.12 02:08, fulcrum-security-memory development wrote:
Tests run: 12, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.82 sec
FAILURE!
Results :
Tests in error:
testGetGroup(org.apache.fulcrum.security.memory.basic.MemoryGroupManagerTest)
Hi General Gump,
On 23.08.12 04:00, fulcrum-parser development wrote:
Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.223 sec
FAILURE!
Results :
Tests in error:
testAddPathInfo(org.apache.fulcrum.parser.ParameterParserTest)
Tests run: 59, Failures: 0, Errors: 1,
Hi Stefan,
On 20.11.11 06:59, Stefan Bodewig wrote:
If it works for a local build then the most likely reason is some sort
of change in SLF4J that it now requires one of the bindings to be
available and didn't require it in the version you get locally.
Well the build works fine locally,
Hi General Gump,
On 19.11.11 05:33, fulcrum-quartz development wrote:
The following work was performed:
http://vmgump.apache.org/gump/public/turbine-fulcrum/fulcrum-quartz-test/gump_work/build_turbine-fulcrum_fulcrum-quartz-test.html
Work Name: build_turbine-fulcrum_fulcrum-quartz-test (Type:
On 01.04.11 06:05, Stefan Bodewig wrote:
Burn a few goats.
Done. Big stench. Nothing changed. What now? ;-)
OK, the way Gump works it means Turbine must be built before Torque, so
we must make torque-generator depend on turbine-core (and obviously
remove the torque dependencies from
Hi General Gump,
This problem started all of a sudden. I hoped it would vanish the same
way. Unfortunately it doesn't. I have no idea what is going on here. The
plugin used to work just fine. Any ideas?
(Please copy d...@turbine.apache.org)
Bye, Thomas.
Original Message
CCed to torque-dev for Thomas Fox to know.
On 31.03.11 16:32, Stefan Bodewig wrote:
Gump will hand out the latest Torque jars, i.e.
torque-runtime-4.0-alpha1-SNAPSHOT.jar,
torque-generator-4.0-alpha1-SNAPSHOT.jar and
torque-templates-4.0-alpha1-SNAPSHOT.jar when asked for Torque. Does
the
general@gump.apache.org wrote:
Running org.apache.torque.avalon.AvalonTest
[DEBUG] Starting container...
[DEBUG] Loading the service container class
org.apache.fulcrum.yaafi.framework.container.ServiceContainerImpl
[DEBUG] Instantiating the service container class
Stefan Bodewig wrote:
OTOH, classpath is completely irrelevant when you use mvn, only the
stuff that is in your POM matters. I don't see a dependency on Avalon
in http://svn.apache.org/viewvc/turbine/fulcrum/trunk/pool/pom.xml or
fulcrum-pool development wrote:
The following work was performed:
http://vmgump.apache.org/gump/public/turbine-fulcrum/fulcrum-pool/gump_work/build_turbine-fulcrum_fulcrum-pool.html
[...]
CLASSPATH:
general@gump.apache.org wrote:
[INFO] Compilation failure
/srv/gump/public/workspace/db-torque/torque-runtime/src/main/java/org/apache/torque/TorqueInstance.java:[460,8]
cannot access org.apache.commons.lang.exception.NestableException
class file for
Stefan Bodewig wrote:
Maven2 support is pretty solid by now, the only major problem we
haven't managed to solve is that of artifact names. You (or anybody
who sees the build failure and wants to fix it) will have to modify
the jar names whenever you change the version since we haven't found
Hi Stefan,
Stefan Bodewig wrote:
The question is whether you want to adapt to commons-lang changes
(there may be good reasons not to) or not. If you want to stick with
commons-lang 2.x, all that we'd need to do is to change the dependency
on commons-lang into one on commons-lang-2.x in your
Thanks for your help. Adding the dependency to maven fixed it.
Bye, Thomas.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
attribute to the dependency to no avail. What else can I do? I cannot
reproduce the problem here.
Thanks in advance,
Thomas Vandahl
Original Message
Subject: [EMAIL PROTECTED]: Project fulcrum-cache (in module
jakarta-turbine-fulcrum) failed
Date: Sat, 30 Dec 2006 05:46:04 PST
From
15 matches
Mail list logo
