The projects jakarta-tomcat-catalina and jakarta-tomcat-4.0 are failing
because the
Didn't notice the incorrect mailing list address at first.
-- Forwarded Message --
Subject: Re: Yes, I broke the Xalan build
Date: Saturday 16 October 2004 01:17
From: Mohammad Isac Niclas bin Abdullah <[EMAIL PROTECTED]>
To: Brian Minchau <[EMAIL PROTECTED]>
Cc: [EMAIL PROTEC
-- Forwarded Message --
Subject: Yes, I broke the Xalan build
Date: Friday 15 October 2004 23:44
From: Brian Minchau <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Niclas,
I was the person who changed the build of some classes in Xalan. The set of
things built
> -Original Message-
> From: Eric Pugh [mailto:[EMAIL PROTECTED]
> Sent: 15 October 2004 14:39
> To: Gump code and data
> Subject: RE: Some progress on Fulcrum Component Builds!
>
> Great news! Last question (well probably not...)
>
> In the latest jakarta-turbine-fulcrum, all the jars
Great news! Last question (well probably not...)
In the latest jakarta-turbine-fulcrum, all the jars are now versioned:
Is this due to some sort of issue with how the projects depend on each
other? In the future, if I bump a version in my project.xml, should I also
fix it here as well?
Eric
I'm receiving GUMP failure warnings as a subscriber to
[EMAIL PROTECTED], and I've ever wondered why spamassassin was tagging
them as spam.
Today I looked at the actual checks they trigger, and found:
4.4 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
Of course I can lower the s
> -Original Message-
> From: Eric Pugh [mailto:[EMAIL PROTECTED]
> Sent: 15 October 2004 13:30
> To: Gump code and data
> Subject: RE: Some progress on Fulcrum Component Builds!
>
> I see! This makes sense! Never thought about the impact on name
changes
> on consumers of your code.
A
Hi,
Solution acquired.
You keep "merlin-unit" in your Maven descriptors.
I have created a new "merlin-unit" project in Gump, which inherits the Jar
from avalon-merlin-unit.
Everyone happy :o)
Niclas
On Friday 15 October 2004 19:29, Eric Pugh wrote:
> I see! This makes sense! Never thought a
I see! This makes sense! Never thought about the impact on name changes
on consumers of your code.. At least not in the way Gump is a consumer.
So, because I use a specific version of merlin-unit, I am fine in my
project. I can't change it to avalon-merlin-unit until the next version
comes out
> -Original Message-
> From: Eric Pugh [mailto:[EMAIL PROTECTED]
> Sent: 15 October 2004 13:11
> To: Gump code and data
> Subject: RE: Some progress on Fulcrum Component Builds!
>
> I am a little confused.. Why is the behavior of avalon-merlin-unit
> special/more difficult then any othe
On Friday 15 October 2004 19:10, Eric Pugh wrote:
> I am a little confused.. Why is the behavior of avalon-merlin-unit
> special/more difficult then any other dependency?
That is due to a name change.
merlin-unit is needed in your Maven descriptor since that has been released
before.
avalon-mer
I am a little confused.. Why is the behavior of avalon-merlin-unit
special/more difficult then any other dependency?
Just as an FYI, my attempt to get fulcrum-crypto-api to build by changing
the dependency from avalon-merlin-unit to merlin-unit failed. I guess that
was reasonable enough. So I h
Excellent. Thanks a lot!
On 15.10.2004 10:53:30 Stefan Bodewig wrote:
> On Fri, 15 Oct 2004, Jeremias Maerki <[EMAIL PROTECTED]>
> wrote:
>
> > It seems like the JUnit task doesn't pick up the test classes that
> > were compiled beforehand.
>
> Yes, because you didn't run unit tests before, it h
On Friday 15 October 2004 19:02, Stephen McConnell wrote:
> Can we just put a symlink in place that links merlin-unit to
> avalon-merlin-unit?.
??
I think the answer lies in the fact that merlin-unit has changed name to
avalon-merlin-unit, and the Magic descriptor should provide a compatibility
> -Original Message-
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
> Sent: 15 October 2004 07:06
> To: Gump code and data
> Subject: Re: Some progress on Fulcrum Component Builds!
>
> On Friday 15 October 2004 07:45, Brett Porter wrote:
> > > > to > > > project="merlin-unit"/>
> > >
On Fri, 15 Oct 2004, Jeremias Maerki <[EMAIL PROTECTED]>
wrote:
> It seems like the JUnit task doesn't pick up the test classes that
> were compiled beforehand.
Yes, because you didn't run unit tests before, it hasn't been part of
the Gump descriptor. I've already fixed it.
Stefan
Dear Gumpmeisters,
The following 3 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but
with warnings.
[EMAIL PROTECTED]: Module werkz success, but with
On Friday 15 October 2004 15:30, Jeremias Maerki wrote:
> Hi Gumpers,
>
> we're currently facing a somewhat strange failure of FOP in Gump. I
> don't have that failure locally. One of the other committers as a
> different error but that's probably related to some weird Xerces problem.
>
> It seems
Hi Gumpers,
we're currently facing a somewhat strange failure of FOP in Gump. I
don't have that failure locally. One of the other committers as a
different error but that's probably related to some weird Xerces problem.
It seems like the JUnit task doesn't pick up the test classes that were
compi
19 matches
Mail list logo
