Re: Gump has hanged...

Niclas Hedhman wrote: http://brutus.apache.org/gump/public/buildLog.html Stopped on the 120th project... the log file doesn't say anything but it did crash somehow. weird. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature

[jira] Created: (GUMP-84) Packages defined in built modules are shown as "green" but they should be "blue"

Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/browse/GUMP-84 Here is an overview of the issue: - Ke

Gump has hanged...

http://brutus.apache.org/gump/public/buildLog.html Stopped on the 120th project... Cheers Niclas -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//---+ -

Betwixt Test Failures

Hello there, the gump project is trying to reach for the 100% build of the ASF java tree. On the way up (we are now at 76% and growing steadily!) we found that betwixt stands in the way. As you can see from http://brutus.apache.org/gump/public/project_todos.html betwixt is now the second most c

Re: jtidy

Only one of those comes from Maven. Until we are building Maven from scratch (as always, ready to talk about this when you are, btw), you'll need to package this one. The other 4 come from 3 different distributions. They could either be added and built (you'll find the statcvs link from maven's pl

jtidy

The jtidy build.xml vanished, so it is Maven or nada. Anybody else tempted to package jtidy -- it is the last step before Cocoon, it seems. That, or somehow we need to tackle this list below. regards Adam The build cannot continue because of the following unsatisfied dependencies: maven-sourcef

BATCH: All dressed up, with nowhere to go...

Dear Gumpmeisters, The following 5 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project icu4j (in module icu4j) success [EMAIL PROTECTED]: Project jaxen (in module jaxen) success [EMAIL PROTECTED]: Project jaxen-t

Re: Cocoon build attempt.

Adam R. B. Jack wrote: We have a problem. Gump tried to build cocoon but it should *NOT* have! Yeah, I had a sneaking suspicion something was wrong there, but I was being hopeful. Ok, I need to go back to the drawing board on 'build from repository'. Basically, the logic was to override the 'prere

Fw: backward incompatible change in org.apache.axis.wsdl.toJava.JavaWriter.writeComment? [ Re: Fw: ws-wsif on Gump

I love seeing such collaboration, especially when Gump initiates it by finding an inconsistency. This took a mere matter of hours start to finish. :-) regards Adam - Original Message - From: "Davanum Srinivas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tues

Re: Cocoon build attempt.

> We have a problem. > > Gump tried to build cocoon but it should *NOT* have! Yeah, I had a sneaking suspicion something was wrong there, but I was being hopeful. Ok, I need to go back to the drawing board on 'build from repository'. Basically, the logic was to override the 'prerequisite failed'

Re: Cocoon build attempt.

Adam Jack wrote: Build from repository is a beautiful thing. Even though Beaver "broke" with a technicality (the LICENSE file was missing) Gump was able (and willing) to take the latest successful build of it from the repository. As such, even though we state Beaver is the "root cause" (despite not

Cocoon build attempt.

Build from repository is a beautiful thing. Even though Beaver "broke" with a technicality (the LICENSE file was missing) Gump was able (and willing) to take the latest successful build of it from the repository. As such, even though we state Beaver is the "root cause" (despite not being a direct d

BATCH: All dressed up, with nowhere to go...

Dear Gumpmeisters, The following 1 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project excalibur-event (in module excalibur) success *** G U M P [EMAIL PROT

JGen on Gump

Dear Sir, In an attempt to see JGen work on Gump, I've added 'notification' e-mails to this project: http://brutus.apache.org/gump/public/jgen/jgen/index.html http://brutus.apache.org/gump/public/jgen/jgen/gump_work/build_jgen_jgen.html Since Gump notifies "from" somebody, I selected your SF.net

Java package sealed?

This is interesting, seems either the package or the whole jar is 'sealed' and so restricts class loading. Not sure why it affects this build, but it does. http://brutus.apache.org/gump/test/jakarta-cactus/jakarta-cactus-framework-12/gump_work/build_jakarta-cactus_jakarta-cactus-framework-12.html

Re: [RT] Standardizing on Maven names

We are, pretty much, we already agreed upon that -- at least for artifact ids. It is just a slow migration, changing them as we detect differences. The "xerces" != "xerces2" is a project name. Since it is so well used it might be quite disruptive to change. I'm open to other's input on if and when

[RT] Standardizing on Maven names

We are having all sort of issues because maven and gump use different naming schemes. Now, why don't we just adopt their naming conventions and live peacefully together from that point on? -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature

Re: Gump descriptors for Fulcrum components.

> On Tue, 12 Oct 2004, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > > > a. The Xerces stuff I don't understand either... Adam? > > xml-xerces is Xerces-J 2 in Gump. xml-xerces2 doesn't exist. There > is xml-xerces1, if you really want that. Yeah, this is annoying. A fundamental difference in nam

Re: Gump descriptors for Fulcrum components.

> How long do I have to wait till the > next run? I see details on when it ran, but not when it will run again. It is an inexact science. The more things build, the longer it takes. It takes about 3-4 hours right now w/ so much building. Basically if we are all working on a certain project/set I

Re: Gump descriptors for Fulcrum components.

> On Tuesday 12 October 2004 18:40, Stefan Bodewig wrote: > > > I have no idea what you'd have to do to make it work with Maven. I > > don't believe there's been a release of beanutils that would reflect > > this change, yet. > > The general rule is; > The "project name" in the element of the Gu

Re: TEST-xxx files available?

Or you might be able to use something like JMeter uses in its build.xml: Some of the output of the test run is logged to this file, which is otherwise not available in a remote Gump. HTH On Tue, 12 Oct 2004 07:56:39 -0600, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > > Is there

[jira] Created: (GUMP-83) The

Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/browse/GUMP-83 Here is an overview of the issue: - Ke

Re: [proposal] remove of

> AFAIK, > Is it? > > IIRC I added to ensure that two different builds inside the > same directory tree didn't affect each other. mockobjects? Yes, I > think so. Basically I was building the same project twice against two > different sets of dependencies. > > Not using but using to different

Re: TEST-xxx files available?

> Is there any way we can have a look at the TEST output for > http://brutus.apache.org/gump/public/excalibur/excalibur-event-impl/gump_work/build_excalibur_excalibur-event-impl.html > If you add this, http://gump.apache.org/metadata/project.html#junitreport, Gump ought show you the files/content

Re: Process for removing Gumped projects?

On Tue, 12 Oct 2004, Eric Pugh <[EMAIL PROTECTED]> wrote: > Since we seem to be doing the "spring cleaning" process for Turbine > and Fulcrum, I wanted to find out the process for removing gumped > projects. I assume just delete the file from /gump/project/. Almost, also remove them from the fil

RE: Gump descriptors for Fulcrum components.

well, it looks like it was removed, so the next gump run shouldn't fail on the xml-xerces2 dependency. I am off to lunch, hopefully it'll be done when we get back! Eric > -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 12, 2004 2:11 PM > To: [

Process for removing Gumped projects?

Hi all, Since we seem to be doing the "spring cleaning" process for Turbine and Fulcrum, I wanted to find out the process for removing gumped projects. I assume just delete the file from /gump/project/. I am thinking of removing jakarta-turbine-jyve jakarta-turbine-origami jakarta-turbine-flux

Re: Gump descriptors for Fulcrum components.

On Tue, 12 Oct 2004, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > a. The Xerces stuff I don't understand either... Adam? xml-xerces is Xerces-J 2 in Gump. xml-xerces2 doesn't exist. There is xml-xerces1, if you really want that. Stefan --

Re: Gump descriptors for Fulcrum components.

On Tuesday 12 October 2004 19:16, Eric Pugh wrote: > Okay.. Starting to get it! So, I noticed that I got another batch of > errors. However, they still are freaking out about the xml-xerces2 > dependency. However, I just checked the jakarta-turbine-fulcrum.xml and > those entities where recentl

BATCH: Unable to send...

Dear Gumpmeisters, The following 2 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project depot-version-test (in module depot) failed [EMAIL PROTECTED]: Project jakarta-hivemind (in module jakarta-hivemind) failed *

BATCH: All dressed up, with nowhere to go...

Dear Gumpmeisters, The following 13 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module jrefactory failed [EMAIL PROTECTED]: Project jai (in module jrefactory) failed [EMAIL PROTECTED]: Project txt2html-task (in m

RE: Gump descriptors for Fulcrum components.

One more thing... Scarab (scarab.tigris.org) uses an older branched version of jakarta-turbine-fulcrum. This produced a single large jar called fulcrum.jar. However, Fulcrum head, and the current item to integrate is a series of seperate components. So, I believe this means that we need to cre

Re: TEST-xxx files available?

On Tue, 12 Oct 2004, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > Hi, > > Is there any way we can have a look at the TEST output for > http://brutus.apache.org/gump/public/excalibur/excalibur-event-impl/gump_work/build_excalibur_excalibur-event-impl.html

RE: Gump descriptors for Fulcrum components.

Okay.. Starting to get it! So, I noticed that I got another batch of errors. However, they still are freaking out about the xml-xerces2 dependency. However, I just checked the jakarta-turbine-fulcrum.xml and those entities where recently removed. How long do I have to wait till the next run?

TEST-xxx files available?

Hi, Is there any way we can have a look at the TEST output for http://brutus.apache.org/gump/public/excalibur/excalibur-event-impl/gump_work/build_excalibur_excalibur-event-impl.html Since this testcase doesn't fail on my local system (and I have been running it many times). Cheers Niclas --

RE: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

> -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 12 October 2004 12:47 > To: [EMAIL PROTECTED] > Subject: Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta- > turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml > logging-log4j-12.xml

Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

On Tue, 12 Oct 2004, Stephen McConnell <[EMAIL PROTECTED]> wrote: > True - I'm just saying that there is a Jakarta Turbine Fulcrum > project within Apache. Sure. 8-) When I said "project", I was talking about the Gump . No offence intended in any way. Stefan --

Re: Gump descriptors for Fulcrum components.

On Tuesday 12 October 2004 18:40, Stefan Bodewig wrote: > I have no idea what you'd have to do to make it work with Maven. I > don't believe there's been a release of beanutils that would reflect > this change, yet. The general rule is; The "project name" in the element of the Gump descriptor m

RE: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

> -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 12 October 2004 12:35 > To: [EMAIL PROTECTED] > Subject: Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta- > turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml > logging-log4j-12.xml

Re: Gump descriptors for Fulcrum components.

On Tuesday 12 October 2004 18:30, Eric Pugh wrote: > Can you supply some information on what we should change them to? To be > honest, I've kinda quit watching the Avalon related mailing lists for the > past while. But I guess, if we are going to participate in Gump builds > (which is a *good* th

Re: Gump descriptors for Fulcrum components.

On Tue, 12 Oct 2004, Eric Pugh <[EMAIL PROTECTED]> wrote: > And what does this error mean? I notice in the gump config file > that there is a dependency on commons-beanutils-core. I changed it after the build failure. commons-beanutils has been split into *-core and *-beanutils-collections. Fo

RE: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

Hi, I think my last email came late into the process. Let me know what I can do to help. I noticed that for the fulcrum-naming component, I was able to remove the xerces implementation and xmlparserapi's from the project.xml and have everything work. When making these types of changes, do I ne

Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

On Tue, 12 Oct 2004, Stephen McConnell <[EMAIL PROTECTED]> wrote: >> -Original Message- From: Stefan Bodewig >> >> There is no jakarta-turbine-fulcrum project (anymore?), > > There sure is. They have a bunch of projects producing a swag of > components. There is a jakarta-turbine-fulcr

RE: Gump descriptors for Fulcrum components.

Can you supply some information on what we should change them to? To be honest, I've kinda quit watching the Avalon related mailing lists for the past while. But I guess, if we are going to participate in Gump builds (which is a *good* thing) then we need to start pacing the latest and greatest c

RE: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

> -Original Message- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: 12 October 2004 11:54 > To: Gump code and data > Subject: Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta- > turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml > logging-log4j-12.xm

Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

On Tuesday 12 October 2004 17:26, Stephen McConnell wrote: > > There is no jakarta-turbine-fulcrum project (anymore?), > > There sure is. They have a bunch of projects producing a swag of > components. Well, there is no "jakarta-turbine-fulcrum" project with that name. Each component is its own

RE: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

> -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: 12 October 2004 10:02 > To: [EMAIL PROTECTED] > Subject: Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta- > turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml > logging-log4j-12.xml

Re: cvs commit: gump/project beaver.xml

On Tue, 12 Oct 2004, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > Should have said that I'm currently looking into it. works now. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECT

Re: cvs commit: gump/project jakarta-turbine-3.xml jakarta-turbine-flux.xml jakarta-turbine-fulcrum.xml jakarta-turbine-site.xml logging-log4j-12.xml maven.xml scarab.xml xml-crimson.xml

On 12 Oct 2004, <[EMAIL PROTECTED]> wrote: > Fix a bunch of broken project names, AFAIU most of them have been autogenerated so we have a mismatch between the Gump plugin in Maven and Gump's view of the world, I'm afraid. There is no jakarta-turbine-fulcrum project (anymore?), Torque has becom

Re: cvs commit: gump/project beaver.xml

On Tue, 12 Oct 2004, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On 11 Oct 2004, <[EMAIL PROTECTED]> wrote: > >> + > > this won't help too much unless you add the dependencies as well, in > particular Ant ;-) Should have said that I'm currently looking into it. Stefan ---

Re: cvs commit: gump/project beaver.xml

On 11 Oct 2004, <[EMAIL PROTECTED]> wrote: > + this won't help too much unless you add the dependencies as well, in particular Ant ;-) Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [E

Re: [proposal] remove of

On Sun, 10 Oct 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > AFAIK, to ensure that two different builds inside the same directory tree didn't affect each other. mockobjects? Yes, I think so. Basically I was building the same project twice against two different sets of dependencies. Not

Re: [proposal] remove of

On Sun, 10 Oct 2004, sebb <[EMAIL PROTECTED]> wrote: > Seems to me that the build files run by Gump should automatically > create any directories they need anyway? Or am I missing something? Yes, the directory have to exists before Ant/Maven is started, creating the during the build is too late.

Re: a few questions on our descriptors

On Sun, 10 Oct 2004, Leo Simons <[EMAIL PROTECTED]> wrote: > I believe the old gump actually had an XSLT snippet which performed > this "macro expansion". No, it has been done in Java. inside of Ant can only specify a single jar while on the outside can depend on more than one - so the code ha

Re: a few questions on our descriptors

On Sun, 10 Oct 2004, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Sunday 10 October 2004 01:38, Stefano Mazzocchi wrote: > >> gosh, this is all very confusing, people. > > No shit. AFAIUI, it is something about feeding the ant script with > additional information need to properly build those p