On Feb 9, 2005, at 10:20 AM, Andrew McIntyre wrote:
So close! One last problem:
Ha! I spoke too soon. Now we're at the last split, but there's yet
another problem. From build_db-derby_derby:
verifysplit:
noSplit:
[echo] * SplitMessages not available *
[echo] * Run all
On 9 Feb 2005, [EMAIL PROTECTED] wrote:
No longer need jakarta-turbine-stratum to be built under gump.
Components moved to jakarta-turbine-fulcrum, jcs, and commons
projects.
Erik, there are at least three projects that depend(ed) on Stratum:
Turbine-2, Turbine-3 and Torque.
How can we
On Wed, 09 Feb 2005, Peter Janes [EMAIL PROTECTED] wrote:
The way to fix the build is to use namespacing,
one way, not *the* way.
The other way is to use the xml descriptor instead of the properties
file as resource in the taskdef.
taskdef resource=net/sf/antcontrib/antlib.xml/
Stefan
On Wed, 9 Feb 2005, Samuel Andrew McIntyre
[EMAIL PROTECTED] wrote:
Not sure why this is happening, as the classpath that the
verifysplit target checks for org.apache.derbyBuild.splitmessages
should be ${basedir}/classes,
which is (err, was ;-) not in your CLASSPATH.
Should work with the
Dear Gumpmeisters,
The following 2 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Project wsfx-axis-types (in module muse) failed
[EMAIL PROTECTED]: Project lenya (in module lenya) failed
Stefan Bodewig wrote:
On Wed, 09 Feb 2005, Peter Janes [EMAIL PROTECTED] wrote:
The way to fix the build is to use namespacing,
one way, not *the* way.
The other way is to use the xml descriptor instead of the properties
file as resource in the taskdef.
Ah, I should have left it to the Ant master
I'm so glad all that was logged and archived. Been a long day and I
didn't clue in that the address used in the nags was the mailing list
address. Thought it was some sort of pun on the military rank like
when General Gump says jump, you jump.
By the way, all of this was brought on by the
Oops, that would have been bad. I was trying to allow nags from
general@gump.apache.org to reach the log4cxx-dev mailing list.
However, my first attempt at mailing list administration almost routed
all the log4cxx-dev messages here. I'll try again not forgetting the
allow-subscribe and make
