Re: Your Gump Build(s)
David Crossley wrote: > Francesco Chicchiriccò wrote: > > David Crossley wrote: > > > > > >Reminder to the Cocoon project: > > > > > >We have a number of Gump builds: > > >See http://svn.apache.org/repos/asf/gump/metadata/project/ > > >for the "cocoon" entries. > > > > > >For example, the output from the vmgump machine is here: > > >http://vmgump.apache.org/gump/public/cocoon3/ > > >and > > >http://vmgump.apache.org/gump/public/cocoon/ for c2.2 > > >(IIRC then cocoon-2.1 is "packaged" rather than built.) > > > > > >The metadata for each Cocoon "project" probably > > >needs some care and attention from us. > > > > Hi David, > > I am not familiar with Gump at all, but at least for Cocoon 3 [1] and > > Cocoon 2.1 [2] we have Jenkins jobs defined. > > Gump is very different. See Stefan's message below. > > I reckon that both are useful in different ways. This is the description from their home page: "Gump is unique in that it builds and compiles software against the latest development versions of those projects. This allows gump to detect potentially incompatible changes to that software just a few hours after those changes are checked into the version control system." and from their Board reports: "Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate." -David > > I don't think we still need Gump, at least for C3 and C2.1 (and we might > > define a job on Jenkins for C2.2 as well), right? > > > > WDYT? Should we safely remove cocoon entries from Gump? How could this > > be done? > > > > Regards. > > > > [1] https://builds.apache.org/job/Cocoon%203.0/ > > [2] https://builds.apache.org/job/Cocoon%202.1.X/ > > > > >Stefan Bodewig wrote: > > >>Dear Community > > >> > > >>Apache Gump builds some of your projects and it is quite possible you > > >>don't know or have by now forgotten about it. > > >> > > >>More than half a year ago a technical problem has forced us to turn off > > >>emails on build failures as we would have been sending out lots of false > > >>alarms. > > >> > > >>Before we re-enable emails we'd like to know whether you are still > > >>interested in the service Gump provides, so please tell us. :-) > > >> > > >>Metadata for many projects have been neglected for a long time and it is > > >>quite possible they'd need some love for results to be meaningful. All > > >>Apache committers have write access to Gump's metadata. > > >> > > >>In case you don't know what this Gump stuff is about: > > >> > > >>Apache Gump builds the full stack of the latest commits of software in > > >>order to ensure integrity over releases. Build failures surface API > > >>discontinuities between projects before they impact releases, and Gump's > > >>e-mail notifications hope to promote the conversations between teams to > > >>resolve those discontinuities. > > >> > > >>When responding to this mail please shorten the CC list as appropriate. > > >> > > >>Cheers > > >> > > >> Stefan > > >> > > >> on behalf of the Gump PMC > > > > -- > > Francesco Chicchiriccò > > > > ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member > > http://people.apache.org/~ilgrosso/ > >
Re: Your Gump Build(s)
Francesco Chicchiriccò wrote: > David Crossley wrote: > > > >Reminder to the Cocoon project: > > > >We have a number of Gump builds: > >See http://svn.apache.org/repos/asf/gump/metadata/project/ > >for the "cocoon" entries. > > > >For example, the output from the vmgump machine is here: > >http://vmgump.apache.org/gump/public/cocoon3/ > >and > >http://vmgump.apache.org/gump/public/cocoon/ for c2.2 > >(IIRC then cocoon-2.1 is "packaged" rather than built.) > > > >The metadata for each Cocoon "project" probably > >needs some care and attention from us. > > Hi David, > I am not familiar with Gump at all, but at least for Cocoon 3 [1] and > Cocoon 2.1 [2] we have Jenkins jobs defined. Gump is very different. See Stefan's message below. I reckon that both are useful in different ways. -David > I don't think we still need Gump, at least for C3 and C2.1 (and we might > define a job on Jenkins for C2.2 as well), right? > > WDYT? Should we safely remove cocoon entries from Gump? How could this > be done? > > Regards. > > [1] https://builds.apache.org/job/Cocoon%203.0/ > [2] https://builds.apache.org/job/Cocoon%202.1.X/ > > >Stefan Bodewig wrote: > >>Dear Community > >> > >>Apache Gump builds some of your projects and it is quite possible you > >>don't know or have by now forgotten about it. > >> > >>More than half a year ago a technical problem has forced us to turn off > >>emails on build failures as we would have been sending out lots of false > >>alarms. > >> > >>Before we re-enable emails we'd like to know whether you are still > >>interested in the service Gump provides, so please tell us. :-) > >> > >>Metadata for many projects have been neglected for a long time and it is > >>quite possible they'd need some love for results to be meaningful. All > >>Apache committers have write access to Gump's metadata. > >> > >>In case you don't know what this Gump stuff is about: > >> > >>Apache Gump builds the full stack of the latest commits of software in > >>order to ensure integrity over releases. Build failures surface API > >>discontinuities between projects before they impact releases, and Gump's > >>e-mail notifications hope to promote the conversations between teams to > >>resolve those discontinuities. > >> > >>When responding to this mail please shorten the CC list as appropriate. > >> > >>Cheers > >> > >> Stefan > >> > >> on behalf of the Gump PMC > > -- > Francesco Chicchiriccò > > ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member > http://people.apache.org/~ilgrosso/ >
Re: Your Gump Build(s)
On 02/07/2013 09:34, David Crossley wrote: Reminder to the Cocoon project: We have a number of Gump builds: See http://svn.apache.org/repos/asf/gump/metadata/project/ for the "cocoon" entries. For example, the output from the vmgump machine is here: http://vmgump.apache.org/gump/public/cocoon3/ and http://vmgump.apache.org/gump/public/cocoon/ for c2.2 (IIRC then cocoon-2.1 is "packaged" rather than built.) The metadata for each Cocoon "project" probably needs some care and attention from us. Hi David, I am not familiar with Gump at all, but at least for Cocoon 3 [1] and Cocoon 2.1 [2] we have Jenkins jobs defined. I don't think we still need Gump, at least for C3 and C2.1 (and we might define a job on Jenkins for C2.2 as well), right? WDYT? Should we safely remove cocoon entries from Gump? How could this be done? Regards. [1] https://builds.apache.org/job/Cocoon%203.0/ [2] https://builds.apache.org/job/Cocoon%202.1.X/ Stefan Bodewig wrote: Dear Community Apache Gump builds some of your projects and it is quite possible you don't know or have by now forgotten about it. More than half a year ago a technical problem has forced us to turn off emails on build failures as we would have been sending out lots of false alarms. Before we re-enable emails we'd like to know whether you are still interested in the service Gump provides, so please tell us. :-) Metadata for many projects have been neglected for a long time and it is quite possible they'd need some love for results to be meaningful. All Apache committers have write access to Gump's metadata. In case you don't know what this Gump stuff is about: Apache Gump builds the full stack of the latest commits of software in order to ensure integrity over releases. Build failures surface API discontinuities between projects before they impact releases, and Gump's e-mail notifications hope to promote the conversations between teams to resolve those discontinuities. When responding to this mail please shorten the CC list as appropriate. Cheers Stefan on behalf of the Gump PMC -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: Your Gump Build(s)
David Crossley wrote: > > Reminder to the Cocoon project: > > We have a number of Gump builds: > See http://svn.apache.org/repos/asf/gump/metadata/project/ > for the "cocoon" entries. > > For example, the output from the vmgump machine is here: > http://vmgump.apache.org/gump/public/cocoon3/ At the moment Cocoon3 is failing with a complaint that seems to be related to FOP. See http://vmgump.apache.org/gump/public/cocoon3/ and follow the link to "cocoon-optional" (which the other cocoon parts depend upon). Then follow the link to the "build_cocoon3_cocoon-optional" output which has the detail. -David > and > http://vmgump.apache.org/gump/public/cocoon/ for c2.2 > (IIRC then cocoon-2.1 is "packaged" rather than built.) > > The metadata for each Cocoon "project" probably > needs some care and attention from us. > > -David > > Stefan Bodewig wrote: > > Dear Community > > > > Apache Gump builds some of your projects and it is quite possible you > > don't know or have by now forgotten about it. > > > > More than half a year ago a technical problem has forced us to turn off > > emails on build failures as we would have been sending out lots of false > > alarms. > > > > Before we re-enable emails we'd like to know whether you are still > > interested in the service Gump provides, so please tell us. :-) > > > > Metadata for many projects have been neglected for a long time and it is > > quite possible they'd need some love for results to be meaningful. All > > Apache committers have write access to Gump's metadata. > > > > In case you don't know what this Gump stuff is about: > > > > Apache Gump builds the full stack of the latest commits of software in > > order to ensure integrity over releases. Build failures surface API > > discontinuities between projects before they impact releases, and Gump's > > e-mail notifications hope to promote the conversations between teams to > > resolve those discontinuities. > > > > When responding to this mail please shorten the CC list as appropriate. > > > > Cheers > > > > Stefan > > > > on behalf of the Gump PMC > >
Re: Your Gump Build(s)
Reminder to the Cocoon project: We have a number of Gump builds: See http://svn.apache.org/repos/asf/gump/metadata/project/ for the "cocoon" entries. For example, the output from the vmgump machine is here: http://vmgump.apache.org/gump/public/cocoon3/ and http://vmgump.apache.org/gump/public/cocoon/ for c2.2 (IIRC then cocoon-2.1 is "packaged" rather than built.) The metadata for each Cocoon "project" probably needs some care and attention from us. -David Stefan Bodewig wrote: > Dear Community > > Apache Gump builds some of your projects and it is quite possible you > don't know or have by now forgotten about it. > > More than half a year ago a technical problem has forced us to turn off > emails on build failures as we would have been sending out lots of false > alarms. > > Before we re-enable emails we'd like to know whether you are still > interested in the service Gump provides, so please tell us. :-) > > Metadata for many projects have been neglected for a long time and it is > quite possible they'd need some love for results to be meaningful. All > Apache committers have write access to Gump's metadata. > > In case you don't know what this Gump stuff is about: > > Apache Gump builds the full stack of the latest commits of software in > order to ensure integrity over releases. Build failures surface API > discontinuities between projects before they impact releases, and Gump's > e-mail notifications hope to promote the conversations between teams to > resolve those discontinuities. > > When responding to this mail please shorten the CC list as appropriate. > > Cheers > > Stefan > > on behalf of the Gump PMC >
Your Gump Build(s)
Dear Community Apache Gump builds some of your projects and it is quite possible you don't know or have by now forgotten about it. More than half a year ago a technical problem has forced us to turn off emails on build failures as we would have been sending out lots of false alarms. Before we re-enable emails we'd like to know whether you are still interested in the service Gump provides, so please tell us. :-) Metadata for many projects have been neglected for a long time and it is quite possible they'd need some love for results to be meaningful. All Apache committers have write access to Gump's metadata. In case you don't know what this Gump stuff is about: Apache Gump builds the full stack of the latest commits of software in order to ensure integrity over releases. Build failures surface API discontinuities between projects before they impact releases, and Gump's e-mail notifications hope to promote the conversations between teams to resolve those discontinuities. When responding to this mail please shorten the CC list as appropriate. Cheers Stefan on behalf of the Gump PMC
Re: State of Cocoon Builds in Gump
On Tue, Jul 27, 2010 at 1:48 AM, Stefan Bodewig wrote: > Hi, > > we've been building a large part of Cocoon 3 and almost everything Lenya > and Coccoon3 need of Cocoon 2.2 for weeks now. [...] > The one remaining failure I can see is in flowscript-impl and this is > due to a backwards incompatible change to the continuation API in rhino > between 1.7R1 and 1.7R2 AFAICT. I guess you already know about that. > > Before I start to fiddle with Gump's config so that Cocoon does not see > rhino's trunk I wanted to ask whether there were any plans to migrate to > the newer continuation API (in which case I wouldn't need to hide > rhino). > Stefan, many thanks for taking this on. I don't expect you will get much response, all of Cocoon seems quite these days. I think it just mostly works so very few people see much reason to touch the code base -- Peter Hunsberger
State of Cocoon Builds in Gump
Hi, we've been building a large part of Cocoon 3 and almost everything Lenya and Coccoon3 need of Cocoon 2.2 for weeks now. Some tests failed initially because Xalan's trunk now requires serializer.jar but I managed to fix that by sneaking in Xalan 2.7.1's POM when Cocoon asks for it so that Cocoon gets serializer.jar via a transitive dependency. If you ever upgrade your Xalan dependencies you will likely add the dependency on serializer anyway. The one remaining failure I can see is in flowscript-impl and this is due to a backwards incompatible change to the continuation API in rhino between 1.7R1 and 1.7R2 AFAICT. I guess you already know about that. Before I start to fiddle with Gump's config so that Cocoon does not see rhino's trunk I wanted to ask whether there were any plans to migrate to the newer continuation API (in which case I wouldn't need to hide rhino). BTW, let me know if you want to enable nagging. Cheers Stefan
Re: [Gump] cocoon-sax build error
On 2010-06-28, Stefan Bodewig wrote: > I'll see whether I can make the Xalan build produce the same jar that > can be found in the mvn repo - looks possible - and once Gump produces > that I think the cocoon-sax build will be fixed. well, sort of <http://gump.zones.apache.org/gump/test/cocoon3/cocoon-sax/index.html> No more classloader issues but a whole lot of test failures. The next Gump run will split the unit tests from building cocoon-sax (by setting maven.test.skip.exec to true) and this should allow the other modules to get built while whoever understand the test failures can work on making them pass without any rush. There will be a new Gump project cocoon-sax-test and surefire reports will be available. Stefan
Re: [Gump] cocoon-sax build error
Hi Stefan, thanks a lot for the incredible analysis you've done!!! Have a nice day, Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Mon, Jun 28, 2010 at 9:21 AM, Stefan Bodewig wrote: > Hi, > > I think I see why the build currently fails in Gump. > > The Xalan jar that can be downloaded from the mvn repository contains > java_cup and bcel and regex and a few other things while the one Gump > currently builds does not. So if you build Cocoon the normal way you > get the additional dependencies for free (and without control over their > version, I may add). > > I'll see whether I can make the Xalan build produce the same jar that > can be found in the mvn repo - looks possible - and once Gump produces > that I think the cocoon-sax build will be fixed. You should be able to > remove the bcel test dependency as well after that. > > Stefan >
[Gump] Cocoon 2.2.x Reactor Build Failure
Hi all, I don't understand reactors, versions and versions of transitive dependencies inside mvn well enough to see where the problem arises, but the build currently fails because cocoon-expression-language-impl or one of its dependencies wants version 1.0.3-SNAPSHOT of cocoon-configuration-api. I can see the jar has previously been installed to the local repository, though. Any ideas? I intend to split up the reactor to build the pieces required by Cocoon 3.x and Lenya sometime later this week or the next, which may solve the issue, but it would be nice to understand what is going on right now. Stefan
[Gump] cocoon-sax build error
Hi, I think I see why the build currently fails in Gump. The Xalan jar that can be downloaded from the mvn repository contains java_cup and bcel and regex and a few other things while the one Gump currently builds does not. So if you build Cocoon the normal way you get the additional dependencies for free (and without control over their version, I may add). I'll see whether I can make the Xalan build produce the same jar that can be found in the mvn repo - looks possible - and once Gump produces that I think the cocoon-sax build will be fixed. You should be able to remove the bcel test dependency as well after that. Stefan
Re: Gump for Cocoon3
On 2010-06-24, David Crossley wrote: > At Apache Gump, Stefan has recently added a Gump build of Cocoon3. thank you for the pointer, David. > Could someone here at Cocoon assist with the build errors. Over the past few months we've found mvn reactor builds to be tricky for various reasons. One of them is that we need to build up the combined dependencies of all components just to build a single one - and another one are cryptic errors like the one we see right now 8-) I'll see whether I can find time to split up the reactor into individual component builds over the next few hours, this may give us something that is easier to target. > Not sure if Gump runs more than once per day, cron would start it every six hours, but it will never start two runs in parallel and since we are close to twelve hours it is more or less one maybe two builds a day. Stefan
Re: Gump for Cocoon3
On 2010-06-24, Stefan Bodewig wrote: > I'll see whether I can find time to split up the reactor into individual > component builds over the next few hours, this may give us something > that is easier to target. This is ready now[1]. The Gump run that started on vmgump a few hours ago won't see it but the next one starting at <http://gump.zones.apache.org/gump/test/buildLog.html> will. I've created individual mvn builds for all modules that cocoon-all depends on and also kept the reactor build as a separate Gump project. It usually takes a few Gump runs until all dependencies have been sorted out - and typos been fixed - but hopefully we'll see parts of Coccon building again soon. Once this is through it would be nice if we could make the 2.2 and 2.1 branches build as well in order to help Cocoon's downstream users. But let's do that one can of worms at a time ... Stefan [1] http://svn.apache.org/repos/asf/gump/metadata/project/cocoon3.xml
Re: Gump for Cocoon3
[resending, original is likely stuck in the moderation queue] On 2010-06-24, David Crossley wrote: > At Apache Gump, Stefan has recently added a Gump build of Cocoon3. thank you for the pointer, David. > Could someone here at Cocoon assist with the build errors. Over the past few months we've found mvn reactor builds to be tricky for various reasons. One of them is that we need to build up the combined dependencies of all components just to build a single one - and another one are cryptic errors like the one we see right now 8-) I'll see whether I can find time to split up the reactor into individual component builds over the next few hours, this may give us something that is easier to target. > Not sure if Gump runs more than once per day, cron would start it every six hours, but it will never start two runs in parallel and since we are close to twelve hours it is more or less one maybe two builds a day. Stefan
Re: Gump for Cocoon3
Hi all, it seems something wrong happens when pre-compiling XSLTs, as Reinhard supposed. I'll try to add the BCEL dependency to fix that, btw I don't understand why it happens... I'll let you know as soon as possible. Thanks!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Thu, Jun 24, 2010 at 10:42 AM, Reinhard Pötz wrote: > David Crossley wrote: >> At Apache Gump, Stefan has recently added a Gump build of Cocoon3. >> >> See http://thread.gmane.org/gmane.comp.jakarta.gump/14458/focus=14475 >> >> Here is the first output: >> http://vmgump.apache.org/gump/public/cocoon3/ >> >> If not familiar with Gump, then follow: >> All Projects : cocoon3 >> then >> Project-level Work : build_cocoon3_cocoon3 >> then >> Output : Complete Output File >> >> Could someone here at Cocoon assist with the build errors. >> >> Not sure if Gump runs more than once per day, >> but that last run finished at 19:20 US PDT. >> >> When it settles, we could enable Gump to "nag" us. > > I guess it is somehow related with the XSLTC precompilation tests. > Simone, any idea? > > -- > Reinhard Pötz Founder & Managing Director, Indoqa > http://www.indoqa.com/people/reinhard-poetz.html > > Member of the Apache Software Foundation > Apache Cocoon Committer, PMC member reinh...@apache.org > >
Re: Gump for Cocoon3
David Crossley wrote: > At Apache Gump, Stefan has recently added a Gump build of Cocoon3. > > See http://thread.gmane.org/gmane.comp.jakarta.gump/14458/focus=14475 > > Here is the first output: > http://vmgump.apache.org/gump/public/cocoon3/ > > If not familiar with Gump, then follow: > All Projects : cocoon3 > then > Project-level Work : build_cocoon3_cocoon3 > then > Output : Complete Output File > > Could someone here at Cocoon assist with the build errors. > > Not sure if Gump runs more than once per day, > but that last run finished at 19:20 US PDT. > > When it settles, we could enable Gump to "nag" us. I guess it is somehow related with the XSLTC precompilation tests. Simone, any idea? -- Reinhard PötzFounder & Managing Director, Indoqa http://www.indoqa.com/people/reinhard-poetz.html Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinh...@apache.org
Gump for Cocoon3
At Apache Gump, Stefan has recently added a Gump build of Cocoon3. See http://thread.gmane.org/gmane.comp.jakarta.gump/14458/focus=14475 Here is the first output: http://vmgump.apache.org/gump/public/cocoon3/ If not familiar with Gump, then follow: All Projects : cocoon3 then Project-level Work : build_cocoon3_cocoon3 then Output : Complete Output File Could someone here at Cocoon assist with the build errors. Not sure if Gump runs more than once per day, but that last run finished at 19:20 US PDT. When it settles, we could enable Gump to "nag" us. -David
Re: What's going on with gump?
I don't know if it helps us just yet, but look what our dear departed friend did recently ... http://marc.theaimsgroup.com/?l=gump&m=114280451625397 [gump3] mavenization2 of dynagump completed -David
Re: What's going on with gump?
On 03.04.2006 17:32, Carsten Ziegeler wrote: I think they are doing this "somehow" by using an own local repository which always delivers the "correct" version. They put the results of building the trunks of our dependencies into this local repository. Jörg
Re: What's going on with gump?
Upayavira wrote: > Ralph Goers wrote: > >> Thanks. I sort of knew all that, but what I guess I'm missing is how it >> actually does what you are saying it does. With a maven2 build how do >> they "force" you to pick up the latest version (actually - I already >> know the answer to that since I have a Jira bug opened on Maven 2 to do >> just that. The answer is, you can't). > > Well, that's the Gump/Maven people's problem to solve, eh? > I think they are doing this "somehow" by using an own local repository which always delivers the "correct" version. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: What's going on with gump?
Ralph Goers wrote: > Upayavira wrote: > >> Ralph Goers wrote: >> >> >>> Reinhard Poetz wrote: >>> >>>> yes, according to the mails above sometime in the future it will work. >>>> >>>> - o - >>>> >>>> If somebody has time to fix gump.xml so that it builds at least >>>> cocoon-core it would be a good idea. If not, we should simply ask the >>>> Gump folks to remove the descriptor. >>>> >>>> WDOT? >>>> >>>> >>> Everytime gump breaks I find myself wondering why anybody cares? Can >>> someone educate me on what is better about gump then us running >>> Continuum? >>> >> >> Firstly, I am no expert on Gump. >> >> You can see Gump as more of a social thing - it not just related to our >> own pretty little project - it builds _everything_. It checks out trunk >> on a huge number of projects and builds them, thus ensuring that all >> projects continue to work together in their trunk versions. So think of >> it as one huge Continuum for _all_ Apache software and beyond, not just >> for Cocoon. >> >> As such, it will tell us if, for some reason, Cocoon wouldn't compile on >> Kaffe, or if one of our dependencies changed its interface and that >> broke our code. >> >> > How can that work? We specify the versions in the pom.xml. It will just > keep rebuilding the same thing until the pom is changed. I guess I'm > not sure how that even worked in the old system since we had all the jar > files in our own repository. Heck, that's the point. Gump ignores specific versions and just builds against trunk for _everything_. That is the point of it - find out quickly if someone broke something. >> Cocoon is a fantastic project for the Gump people, because we have s >> many dependencies. If Cocoon builds, that means all of its dependencies, >> and their dependencies, etc, all built too, which as I understand it >> doesn't happen that often :-) >> >> > See the above comment. How does that happen if we still have the old > version? See above answer :-) >> So, yes, it is a valuable resource, but on a broader scale than just our >> own project. > Thanks. I sort of knew all that, but what I guess I'm missing is how it > actually does what you are saying it does. With a maven2 build how do > they "force" you to pick up the latest version (actually - I already > know the answer to that since I have a Jira bug opened on Maven 2 to do > just that. The answer is, you can't). Well, that's the Gump/Maven people's problem to solve, eh? Heck, I said I was no gump expert :-) Regards, Upayavira
Re: What's going on with gump?
Upayavira wrote: Ralph Goers wrote: Reinhard Poetz wrote: yes, according to the mails above sometime in the future it will work. - o - If somebody has time to fix gump.xml so that it builds at least cocoon-core it would be a good idea. If not, we should simply ask the Gump folks to remove the descriptor. WDOT? Everytime gump breaks I find myself wondering why anybody cares? Can someone educate me on what is better about gump then us running Continuum? Firstly, I am no expert on Gump. You can see Gump as more of a social thing - it not just related to our own pretty little project - it builds _everything_. It checks out trunk on a huge number of projects and builds them, thus ensuring that all projects continue to work together in their trunk versions. So think of it as one huge Continuum for _all_ Apache software and beyond, not just for Cocoon. As such, it will tell us if, for some reason, Cocoon wouldn't compile on Kaffe, or if one of our dependencies changed its interface and that broke our code. How can that work? We specify the versions in the pom.xml. It will just keep rebuilding the same thing until the pom is changed. I guess I'm not sure how that even worked in the old system since we had all the jar files in our own repository. Cocoon is a fantastic project for the Gump people, because we have s many dependencies. If Cocoon builds, that means all of its dependencies, and their dependencies, etc, all built too, which as I understand it doesn't happen that often :-) See the above comment. How does that happen if we still have the old version? So, yes, it is a valuable resource, but on a broader scale than just our own project. Regards, Upayavira Thanks. I sort of knew all that, but what I guess I'm missing is how it actually does what you are saying it does. With a maven2 build how do they "force" you to pick up the latest version (actually - I already know the answer to that since I have a Jira bug opened on Maven 2 to do just that. The answer is, you can't). Ralph
Re: What's going on with gump?
Ralph Goers wrote: > > > Reinhard Poetz wrote: >> >> yes, according to the mails above sometime in the future it will work. >> >>- o - >> >> If somebody has time to fix gump.xml so that it builds at least >> cocoon-core it would be a good idea. If not, we should simply ask the >> Gump folks to remove the descriptor. >> >> WDOT? >> > Everytime gump breaks I find myself wondering why anybody cares? Can > someone educate me on what is better about gump then us running Continuum? Firstly, I am no expert on Gump. You can see Gump as more of a social thing - it not just related to our own pretty little project - it builds _everything_. It checks out trunk on a huge number of projects and builds them, thus ensuring that all projects continue to work together in their trunk versions. So think of it as one huge Continuum for _all_ Apache software and beyond, not just for Cocoon. As such, it will tell us if, for some reason, Cocoon wouldn't compile on Kaffe, or if one of our dependencies changed its interface and that broke our code. Cocoon is a fantastic project for the Gump people, because we have s many dependencies. If Cocoon builds, that means all of its dependencies, and their dependencies, etc, all built too, which as I understand it doesn't happen that often :-) So, yes, it is a valuable resource, but on a broader scale than just our own project. Regards, Upayavira
Re: What's going on with gump?
Reinhard Poetz wrote: yes, according to the mails above sometime in the future it will work. - o - If somebody has time to fix gump.xml so that it builds at least cocoon-core it would be a good idea. If not, we should simply ask the Gump folks to remove the descriptor. WDOT? Everytime gump breaks I find myself wondering why anybody cares? Can someone educate me on what is better about gump then us running Continuum? Ralph
Re: What's going on with gump?
Bertrand Delacretaz wrote: > Le 3 avr. 06 à 10:51, Reinhard Poetz a écrit : > >> ...More generally, we need to decide what we do with it as gump.xml as >> it is today is totally broken because of the move to Maven 2... > > While gump is unable to build our trunk, we could at least have it build > the 2.1.x branch? > > I assume this requires pointing gump to the old 2.1.x descriptor, but I > don't know how to do that. The point of having the SVN external was that all Apache committers have commit rights to the Gump area. So, if someone wanted to have Gump build 2.1.x (which makes some sense to me), it would be: a) Check that's okay with the Gump community b) Commit the 2.1.X gump.xml on top of the existing one in the gump SVN c) Create an SVN external in 2.1.X SVN to the gump SVN Upayavira
Re: What's going on with gump?
Le 3 avr. 06 à 10:51, Reinhard Poetz a écrit : ...More generally, we need to decide what we do with it as gump.xml as it is today is totally broken because of the move to Maven 2... While gump is unable to build our trunk, we could at least have it build the 2.1.x branch? I assume this requires pointing gump to the old 2.1.x descriptor, but I don't know how to do that. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: What's going on with gump?
Upayavira wrote:
Reinhard Poetz wrote:
Upayavira wrote:
Reinhard Poetz wrote:
Bertrand Delacretaz wrote:
Le 3 avr. 06 à 09:08, Gump a écrit :
... -DEBUG- Sole output [chaperon-20040205.jar] identifier set to
project name
-INFO- Failed with reason missing build outputs
-ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/
lib/optional/chaperon-20040205.jar
-ERROR- No such directory (where output is expected) : /usr/local/
gump/public/workspace/cocoon/lib/optional...
What's up here? Is gump trying to build the trunk with the old ant
build system?
I'm not too sure about where to look for details on what exactly
gump is trying to do
The error above seems to be caused by the missing lib/optional directory
as I removed them last week.
If somebody wants to reactivate gump again, he should start
incrementally and write a gump descriptor for cocoon-core but please
make sure that we don't have any svn:externals in trunk; I removed the
svn:externals link to gump.xml.
Well that is going to break things. That SVN external was to allow Gump
people write access to our gump descriptor. How come you removed it? It
was placed there in discussion with this list and with the Gump peeps.
Sorry for not bringing this issue to the list.
IIUC I didn't delete the descriptor but only the link to it as gump.xml
is located in the gump SVN. We can add the svn:external to our
repository for convenience but please don't do it within trunk -
/cocoon/gump would be a better idea IMHO.
Actually, this is fair enough, as we no longer depend upon Gump for our
build process.
- o -
More generally, we need to decide what we do with it as gump.xml as it
is today is totally broken because of the move to Maven 2 (e.g. we are
relying on many libraries within the repository; many source directories
have changed, etc.).
Basically the gump descriptor expresses the same dependencies as the
pom.xml and I doubt our community will take care of both. BTW, is
anybody taking care of a working Gump descriptor? The best solution
would be Gump that can work based on pom.xml descriptors ...
I did see some discussion on Gump working with Maven2, but have since
unsubscribed from [EMAIL PROTECTED], as I was hardly reading it.
Found this thread: http://marc.theaimsgroup.com/?t=11434754172&r=1&w=2
So in time, maybe Gump itself will run off pom files where they exis
yes, according to the mails above sometime in the future it will work.
- o -
If somebody has time to fix gump.xml so that it builds at least cocoon-core it
would be a good idea. If not, we should simply ask the Gump folks to remove the
descriptor.
WDOT?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: What's going on with gump?
Reinhard Poetz wrote: > Upayavira wrote: >> Reinhard Poetz wrote: >> >>> Bertrand Delacretaz wrote: >>> >>>> Le 3 avr. 06 à 09:08, Gump a écrit : >>>> >>>> >>>>> ... -DEBUG- Sole output [chaperon-20040205.jar] identifier set to >>>>> project name >>>>> -INFO- Failed with reason missing build outputs >>>>> -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/ >>>>> lib/optional/chaperon-20040205.jar >>>>> -ERROR- No such directory (where output is expected) : /usr/local/ >>>>> gump/public/workspace/cocoon/lib/optional... >>>> >>>> >>>> What's up here? Is gump trying to build the trunk with the old ant >>>> build system? >>>> >>>> I'm not too sure about where to look for details on what exactly >>>> gump is trying to do >>> >>> The error above seems to be caused by the missing lib/optional directory >>> as I removed them last week. >>> >>> If somebody wants to reactivate gump again, he should start >>> incrementally and write a gump descriptor for cocoon-core but please >>> make sure that we don't have any svn:externals in trunk; I removed the >>> svn:externals link to gump.xml. >> >> >> Well that is going to break things. That SVN external was to allow Gump >> people write access to our gump descriptor. How come you removed it? It >> was placed there in discussion with this list and with the Gump peeps. > > Sorry for not bringing this issue to the list. > IIUC I didn't delete the descriptor but only the link to it as gump.xml > is located in the gump SVN. We can add the svn:external to our > repository for convenience but please don't do it within trunk - > /cocoon/gump would be a better idea IMHO. Actually, this is fair enough, as we no longer depend upon Gump for our build process. >- o - > > More generally, we need to decide what we do with it as gump.xml as it > is today is totally broken because of the move to Maven 2 (e.g. we are > relying on many libraries within the repository; many source directories > have changed, etc.). > > Basically the gump descriptor expresses the same dependencies as the > pom.xml and I doubt our community will take care of both. BTW, is > anybody taking care of a working Gump descriptor? The best solution > would be Gump that can work based on pom.xml descriptors ... I did see some discussion on Gump working with Maven2, but have since unsubscribed from [EMAIL PROTECTED], as I was hardly reading it. So in time, maybe Gump itself will run off pom files where they exist. Regards, Upayavira
Re: What's going on with gump?
Upayavira wrote:
Reinhard Poetz wrote:
Bertrand Delacretaz wrote:
Le 3 avr. 06 à 09:08, Gump a écrit :
... -DEBUG- Sole output [chaperon-20040205.jar] identifier set to
project name
-INFO- Failed with reason missing build outputs
-ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/
lib/optional/chaperon-20040205.jar
-ERROR- No such directory (where output is expected) : /usr/local/
gump/public/workspace/cocoon/lib/optional...
What's up here? Is gump trying to build the trunk with the old ant
build system?
I'm not too sure about where to look for details on what exactly gump
is trying to do
The error above seems to be caused by the missing lib/optional directory
as I removed them last week.
If somebody wants to reactivate gump again, he should start
incrementally and write a gump descriptor for cocoon-core but please
make sure that we don't have any svn:externals in trunk; I removed the
svn:externals link to gump.xml.
Well that is going to break things. That SVN external was to allow Gump
people write access to our gump descriptor. How come you removed it? It
was placed there in discussion with this list and with the Gump peeps.
Sorry for not bringing this issue to the list.
IIUC I didn't delete the descriptor but only the link to it as gump.xml is
located in the gump SVN. We can add the svn:external to our repository for
convenience but please don't do it within trunk - /cocoon/gump would be a better
idea IMHO.
- o -
More generally, we need to decide what we do with it as gump.xml as it is today
is totally broken because of the move to Maven 2 (e.g. we are relying on many
libraries within the repository; many source directories have changed, etc.).
Basically the gump descriptor expresses the same dependencies as the pom.xml and
I doubt our community will take care of both. BTW, is anybody taking care of a
working Gump descriptor? The best solution would be Gump that can work based on
pom.xml descriptors ...
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: What's going on with gump?
Reinhard Poetz wrote: > Bertrand Delacretaz wrote: >> Le 3 avr. 06 à 09:08, Gump a écrit : >> >>> ... -DEBUG- Sole output [chaperon-20040205.jar] identifier set to >>> project name >>> -INFO- Failed with reason missing build outputs >>> -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/ >>> lib/optional/chaperon-20040205.jar >>> -ERROR- No such directory (where output is expected) : /usr/local/ >>> gump/public/workspace/cocoon/lib/optional... >> >> >> What's up here? Is gump trying to build the trunk with the old ant >> build system? >> >> I'm not too sure about where to look for details on what exactly gump >> is trying to do > > The error above seems to be caused by the missing lib/optional directory > as I removed them last week. > > If somebody wants to reactivate gump again, he should start > incrementally and write a gump descriptor for cocoon-core but please > make sure that we don't have any svn:externals in trunk; I removed the > svn:externals link to gump.xml. Well that is going to break things. That SVN external was to allow Gump people write access to our gump descriptor. How come you removed it? It was placed there in discussion with this list and with the Gump peeps. Regards, Upayavira
Re: What's going on with gump?
Bertrand Delacretaz wrote:
Le 3 avr. 06 à 09:08, Gump a écrit :
... -DEBUG- Sole output [chaperon-20040205.jar] identifier set to
project name
-INFO- Failed with reason missing build outputs
-ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/
lib/optional/chaperon-20040205.jar
-ERROR- No such directory (where output is expected) : /usr/local/
gump/public/workspace/cocoon/lib/optional...
What's up here? Is gump trying to build the trunk with the old ant
build system?
I'm not too sure about where to look for details on what exactly gump
is trying to do
The error above seems to be caused by the missing lib/optional directory as I
removed them last week.
If somebody wants to reactivate gump again, he should start incrementally and
write a gump descriptor for cocoon-core but please make sure that we don't have
any svn:externals in trunk; I removed the svn:externals link to gump.xml.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
What's going on with gump? (was: [EMAIL PROTECTED]: Project chaperon (in module cocoon) failed)
Le 3 avr. 06 à 09:08, Gump a écrit : ... -DEBUG- Sole output [chaperon-20040205.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/ lib/optional/chaperon-20040205.jar -ERROR- No such directory (where output is expected) : /usr/local/ gump/public/workspace/cocoon/lib/optional... What's up here? Is gump trying to build the trunk with the old ant build system? I'm not too sure about where to look for details on what exactly gump is trying to do -Bertrand smime.p7s Description: S/MIME cryptographic signature
funny Gump failure
Hello, I wondered why we did not get any Gump message in the last days and had a look at the Cocoon's Gump page [1]. And what depressing do I have to read there: This project failed due to: Project: struts-core Cocoon depends on Struts - that's really hard! ;) It does not directly depend on it, but JCS does - why ever a helper lib like a caching system depends on a web application framework. Jörg [1] http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html
Re: [GUMP] Which jar is supposed to contain CocoonTestCase?
On 08.11.2005 21:30, Stefan Bodewig wrote: there are a few block builds failing because the CocoonTestCase class cannot be found. I assumed it'd be in cocoon-testcase.jar, but this here is what gets created on vmgump: http://svn.apache.org/viewcvs?rev=331881&view=rev hopefully fixes it. Don't know why all other files were excluded. From the commit message it was a sync with our 2.1 branch, but maybe the other files are wrongly excluded there too? I don't want to touch it before the release tomorrow though. Jörg
[GUMP] Which jar is supposed to contain CocoonTestCase?
Hi all, there are a few block builds failing because the CocoonTestCase class cannot be found. I assumed it'd be in cocoon-testcase.jar, but this here is what gets created on vmgump: zip info: META-INF/ has 4 bytes of extra data Archive: cocoon-testcase.jar testing: META-INF/OK testing: META-INF/MANIFEST.MF OK testing: org/ OK testing: org/apache/ OK testing: org/apache/cocoon/ OK testing: org/apache/cocoon/SitemapComponentTestCase.class OK testing: org/apache/cocoon/components/ OK testing: org/apache/cocoon/components/source/ OK testing: org/apache/cocoon/components/source/SourceResolverAdapter.class OK testing: org/apache/cocoon/core/ OK testing: org/apache/cocoon/core/container/ OK testing: org/apache/cocoon/core/container/ContainerTestCase$DefaultLoggerManager.class OK testing: org/apache/cocoon/core/container/ContainerTestCase.class OK testing: org/apache/cocoon/environment/ OK testing: org/apache/cocoon/environment/mock/ OK testing: org/apache/cocoon/environment/mock/MockContext.class OK testing: org/apache/cocoon/environment/mock/MockCookie.class OK testing: org/apache/cocoon/environment/mock/MockEnvironment.class OK testing: org/apache/cocoon/environment/mock/MockRedirector.class OK testing: org/apache/cocoon/environment/mock/MockRequest.class OK testing: org/apache/cocoon/environment/mock/MockResponse.class OK testing: org/apache/cocoon/environment/mock/MockSession.class OK testing: org/apache/cocoon/xml/ OK testing: org/apache/cocoon/xml/WhitespaceFilter.class OK testing: META-INF/INDEX.LIST OK No errors detected in compressed data of cocoon-testcase.jar. test of cocoon-testcase.jar OK Is the class supposed to be in there? Is it excluded by accident? Or do we need to dive into Ant to see whether the problem is there? Stefan
Re: [GUMP vmgump]: Project cowarp (in module cocoon) failed
> Project cowarp has an issue affecting its community integration. > Full details are available at: > http://vmgump.apache.org/gump/public/cocoon/cowarp/index.html > -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/cowarp-0.4.jar Please don't forget to update gump descriptor - or let the project be built by gump. Jörg
Re: Maven, Gump and Blocks
Carsten Ziegeler wrote: ... > Now, we could for example use continuum - whatever that means... > But perhaps pushing gump and maven a little bit could help. http://wiki.apache.org/gump/GumpAndMaven -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: Maven, Gump and Blocks
Daniel Fagerstrom wrote: > > Why is that, I thought the Maven community had stopped being against Gump. > Don't ask me, ask the maven community :) I just looked at this: http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix > >>I think gump is a great thing and it helps a lot, but I think also that >>getting gump using m2 projects is not our concern. >> > > I would like to agree, but it seem to imply that we are going to mean > that we will be without continuous integration until someone else takes > care about it. I doubt that we can afford that in the long term. > Now, we could for example use continuum - whatever that means... But perhaps pushing gump and maven a little bit could help. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Maven, Gump and Blocks
Carsten Ziegeler wrote: Daniel Fagerstrom wrote: Studied the question a little bit more. There is a Maven1 plugin for creating gump.xml from POMs http://maven.apache.org/reference/plugins/gump/, no port to m2 yet though. The plugin is written in Jelly while m2 plugins are written in Java so it takes some work to port it. According to the maven plugin matrix, a gump module is not planned for m2 - the maven advice is to use continuum Why is that, I thought the Maven community had stopped being against Gump. I think gump is a great thing and it helps a lot, but I think also that getting gump using m2 projects is not our concern. I would like to agree, but it seem to imply that we are going to mean that we will be without continuous integration until someone else takes care about it. I doubt that we can afford that in the long term. This is something the maven and gump guys can do. Your answer above seem to indicate that the Maven guys not are going to do it, are there any plans for m2 support from the Gump camp? /Daniel
Re: Maven, Gump and Blocks
Daniel Fagerstrom wrote: > Studied the question a little bit more. There is a Maven1 plugin for > creating gump.xml from POMs > http://maven.apache.org/reference/plugins/gump/, no port to m2 yet > though. The plugin is written in Jelly while m2 plugins are written in > Java so it takes some work to port it. > According to the maven plugin matrix, a gump module is not planned for m2 - the maven advice is to use continuum I think gump is a great thing and it helps a lot, but I think also that getting gump using m2 projects is not our concern. This is something the maven and gump guys can do. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Maven, Gump and Blocks
Was: Re: [2.2] Past, present and future of the maven build Daniel Fagerstrom wrote: Carsten Ziegeler wrote: ... I think compiling a block with m2 is not a problem at all, just define a pom with all dependencies and invoke "m2 install" :) Now, it would be great if someone would start adding poms with dependencies to the blocks... Ok, get the message ;) Some thinking and planning is IMO needed though. We allready have all (or most) dependency info for blocks in gump.xml. Keeping a global gump.xml and block local POMs in synch doesn't sound like that much fun. So, could we move the block parts of the global gump.xml into the blocks, so that we have the POMs and gump.xml at the same place. Or better, can we generate the gump.xml from the POMs. Or even better, is there some integration between gump and Maven, so that Gump can use the POMs? Studied the question a little bit more. There is a Maven1 plugin for creating gump.xml from POMs http://maven.apache.org/reference/plugins/gump/, no port to m2 yet though. The plugin is written in Jelly while m2 plugins are written in Java so it takes some work to port it. IMO the nicest solution would be to describe the dependency structure with POMs, with some extra propoerties for Gump specific things: http://maven.apache.org/reference/plugins/gump/properties.html. Then the gump.xml will be automatically generated by the gump plugin. The first version of the POMs could probably generated with xslt from the current gump.xml. I'm not a volonter, want to focus on the real blocks. WDYT? /Daniel
[GUMP@vmgump]: Project cocoon-block-jcr (in module cocoon) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-jcr has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon-block-jcr : A "jcr:" protocol for Cocoon
Full details are available at:
http://vmgump.apache.org/gump/public/cocoon/cocoon-block-jcr/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole output [jcr-block.jar] identifier set to project name
-INFO- Failed with reason build failed
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/cocoon/cocoon-block-jcr/gump_work/build_cocoon_cocoon-block-jcr.html
Work Name: build_cocoon_cocoon-block-jcr (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only -Dversion=21072005 -Dblock-name=jcr jcr-block
[Working Directory: /usr/local/gump/public/workspace/cocoon]
CLASSPATH:
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-21072005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-21072005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-21072005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-21072005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-21072005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-21072005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-21072005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-21072005.jar:/usr/local/gump/public/workspace/excalibur/components/xmlutil/target/excalibur-xmlutil-21072005.jar:/usr/local/gump/public/workspace/excalibur/components/store/target/excalibur-store-21072005.jar:/usr/local/gump/public/workspace/excalibur/components/pool/api/target/excalibur-pool-api-21072005.jar:/usr/local/gump/public/workspace/excalibur/components/pool/impl/target/excalibur-pool-impl-21072005.jar:/usr/local/gump/public/workspace/excalibur/components/pool/instrumented/target/excalibur-pool-instrumented-21072005.jar:/usr/local/gump/public/workspace/excalibur/containerkit/logger/target/excalibur-logger-21072005.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-21072005.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jakarta-turbine-jcs/target/jcs-21072005.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-21072005.jar:/usr/local/gump/public/workspace/jakarta-commons/httpclient/dist/commons-httpclient.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21072005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21072005.jar:/usr/local/gump/public/workspace/jakarta-commons/jxpath/dist/commons-jxpath.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-21072005.jar:/usr/local
Re: Cocoon Gump descriptor is now in Gump's SVN
Stefano Mazzocchi wrote: Stefano Mazzocchi wrote: Stefan Bodewig wrote: Hi, after we've migrated Gump's metadata over to svn as well, there shouldn't be any need to keep the Cocoon descriptor inside of the cocoon tree. I've just committed , | Added: | gump/metadata/project/cocoon.xml | - copied unchanged from r216130, cocoon/trunk/gump.xml ` and with svn:externals of gump.xml https::/svn.apache.org/repos/asf/gump/metadata/project/cocoon.xml on the cocoon directory you'd have your local copy - and all of you and all of us can change it. Starting with the next Gump run, Gump will use the copy of its own. Finally!!! I'll make that happen. Stefan++!! Oh, crap! SVN can't externalize a file, but only a directory!!! what do we do now ?!? Grant them all write access to the gump.xml file using asf-authorization? I've tried locally giving access to a single file and it works. Regards, Upayavira
Re: Cocoon Gump descriptor is now in Gump's SVN
Stefano Mazzocchi wrote: > Stefan Bodewig wrote: > >>Hi, >> >>after we've migrated Gump's metadata over to svn as well, there >>shouldn't be any need to keep the Cocoon descriptor inside of the >>cocoon tree. >> >>I've just committed >> >>, >>| Added: >>| gump/metadata/project/cocoon.xml >>| - copied unchanged from r216130, cocoon/trunk/gump.xml >>` >> >>and with svn:externals of >> >>gump.xml https::/svn.apache.org/repos/asf/gump/metadata/project/cocoon.xml >> >>on the cocoon directory you'd have your local copy - and all of you >>and all of us can change it. >> >>Starting with the next Gump run, Gump will use the copy of its own. > > > Finally!!! > > I'll make that happen. > > Stefan++!! Oh, crap! SVN can't externalize a file, but only a directory!!! what do we do now ?!? -- Stefano.
Re: Cocoon Gump descriptor is now in Gump's SVN
Stefan Bodewig wrote: > Hi, > > after we've migrated Gump's metadata over to svn as well, there > shouldn't be any need to keep the Cocoon descriptor inside of the > cocoon tree. > > I've just committed > > , > | Added: > | gump/metadata/project/cocoon.xml > | - copied unchanged from r216130, cocoon/trunk/gump.xml > ` > > and with svn:externals of > > gump.xml https::/svn.apache.org/repos/asf/gump/metadata/project/cocoon.xml > > on the cocoon directory you'd have your local copy - and all of you > and all of us can change it. > > Starting with the next Gump run, Gump will use the copy of its own. Finally!!! I'll make that happen. Stefan++!! -- Stefano.
Cocoon Gump descriptor is now in Gump's SVN
Hi, after we've migrated Gump's metadata over to svn as well, there shouldn't be any need to keep the Cocoon descriptor inside of the cocoon tree. I've just committed , | Added: | gump/metadata/project/cocoon.xml | - copied unchanged from r216130, cocoon/trunk/gump.xml ` and with svn:externals of gump.xml https::/svn.apache.org/repos/asf/gump/metadata/project/cocoon.xml on the cocoon directory you'd have your local copy - and all of you and all of us can change it. Starting with the next Gump run, Gump will use the copy of its own. Cheers Stefan
[GUMP@vmgump]: Project cocoon (in module cocoon) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon has an issue affecting its community integration.
This issue affects 50 projects,
and has been outstanding for 6 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon : Java XML Framework
- cocoon-block-apples : Java XML Framework
- cocoon-block-asciiart : Java XML Framework
- cocoon-block-authentication-fw : Java XML Framework
- cocoon-block-axis : Java XML Framework
- cocoon-block-batik : Java XML Framework
- cocoon-block-bsf : Java XML Framework
- cocoon-block-chaperon : Java XML Framework
- cocoon-block-cron : Java XML Framework
- cocoon-block-databases : Java XML Framework
- cocoon-block-deli : Java XML Framework
- cocoon-block-eventcache : Java XML Framework
- cocoon-block-faces : Java XML Framework
- cocoon-block-fop : Java XML Framework
- cocoon-block-forms : Java XML Framework
- cocoon-block-hsqldb : Java XML Framework
- cocoon-block-html : Java XML Framework
- cocoon-block-itext : Java XML Framework
- cocoon-block-javaflow : Java XML Framework
- cocoon-block-jcr : A "jcr:" protocol for Cocoon
- cocoon-block-jfor : Java XML Framework
- cocoon-block-jms : Java XML Framework
- cocoon-block-jsp : Java XML Framework
- cocoon-block-linkrewriter : Java XML Framework
- cocoon-block-mail : Java XML Framework
- cocoon-block-midi : Java XML Framework
- cocoon-block-naming : Java XML Framework
- cocoon-block-paranoid : Java XML Framework
- cocoon-block-petstore : Java XML Framework
- cocoon-block-portal : Java XML Framework
- cocoon-block-profiler : Java XML Framework
- cocoon-block-proxy : Java XML Framework
- cocoon-block-python : Java XML Framework
- cocoon-block-qdox : Java XML Framework
- cocoon-block-repository : Java XML Framework
- cocoon-block-scratchpad : Java XML Framework
- cocoon-block-serializers : Java XML Framework
- cocoon-block-session-fw : Java XML Framework
- cocoon-block-slop : Java XML Framework
- cocoon-block-spring-app : A demo for Spring and Cocoon
- cocoon-block-stx : Java XML Framework
- cocoon-block-taglib : Java XML Framework
- cocoon-block-template : Java XML Framework
- cocoon-block-tour : Java XML Framework
- cocoon-block-velocity : Java XML Framework
- cocoon-block-web3 : Java XML Framework
- cocoon-block-xmldb : Java XML Framework
- cocoon-block-xsp : Java XML Framework
- forrest : Apache Forrest is an XML standards-oriented documentation fr...
- forrest-test : Apache Forrest is an XML standards-oriented documentation
fr...
Full details are available at:
http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon]
-DEBUG- Output [cocoon-testcase.jar] identifier set to output basename:
[cocoon-testcase]
-DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename:
[cocoon-deprecated]
-DEBUG- Dependency on avalon-framework-api exists, no need to add for property
avalonapi.jar.
-INFO- Made directory
[/usr/local/gump/public/workspace/cocoon/build/cocoon-05072005/test]
-INFO- Failed with reason build failed
-INFO- Project Reports in:
/usr/local/gump/public/workspace/cocoon/build/cocoon-05072005/test/output
-WARNING- No directory
[/usr/local/gump/public/workspace/cocoon/build/cocoon-05072005/test/output]
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html
Work Name: build_cocoon_cocoon (Type: Build)
Work ended in a state of : Failed
Elapsed: 14 secs
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only
-Davalonapi.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-05072005.jar
-Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-05072005.jar
-Dbuild=build/cocoon-05072005 gump-core
[Working Directory: /usr/local/gump/public/workspace/cocoon]
CLASSPATH:
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon
Re: [vote] gump-related stuff
Stefano Mazzocchi wrote: We should try to make it easier for gump to work with us. Our build system is a little hacky in that regard since it uses partial gump information to build cocoon. Gump strongly suggests people to move their gump descriptors over to the gump repository, so that all apache committers have access to it, not just cocoon committers. This increases the ability for others to fix the problems that we might introduce. At the same time, this is not possible, since our build depends on that *and* we can't svn:externalize it because the gump metadata is not (yet!) in SVN (we could get it from viewcvs, though, but it sounds hacky) So, the easiest thing is to allow gump committers to modify our 'gump.xml' files. So, issue #1: would you like to allow this? +1 - o - There is another issue: cocoon has unique packages that we only depend on and we place them in our gump.xml file, problem is that later on other projects might start using those and collisions might happen. Gump is not really happy when naming collisions happen (its datamodel is not namespaced, yet) so one way to do it better is to ask the gump folks to package the things we depend on directly. Means that its a little slower turnover. So, issue #2, would you like to ask the gump people to move our library dependencies currently in gump.xml over in the gump metadata repository instead? +1 /Daniel
Re: [vote] gump-related stuff
> --- Ursprüngliche Nachricht --- > Von: Stefano Mazzocchi > Datum: Fri, 17 Jun 2005 08:37:25 -0400 > > So, the easiest thing is to allow gump committers to modify our > 'gump.xml' files. > > So, issue #1: would you like to allow this? +1 > So, issue #2, would you like to ask the gump people to move our library > dependencies currently in gump.xml over in the gump metadata repository > instead? +1 Why not? If we do not have to maintain them ... What should be the downsides? Joerg -- Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie! Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
Re: [vote] gump-related stuff
Stefano Mazzocchi wrote: We should try to make it easier for gump to work with us. Our build system is a little hacky in that regard since it uses partial gump information to build cocoon. Gump strongly suggests people to move their gump descriptors over to the gump repository, so that all apache committers have access to it, not just cocoon committers. This increases the ability for others to fix the problems that we might introduce. At the same time, this is not possible, since our build depends on that *and* we can't svn:externalize it because the gump metadata is not (yet!) in SVN (we could get it from viewcvs, though, but it sounds hacky) So, the easiest thing is to allow gump committers to modify our 'gump.xml' files. So, issue #1: would you like to allow this? +1. Let's knowledged gumpers fix the descriptor when then find errors rather than having to send patches. - o - There is another issue: cocoon has unique packages that we only depend on and we place them in our gump.xml file, problem is that later on other projects might start using those and collisions might happen. Gump is not really happy when naming collisions happen (its datamodel is not namespaced, yet) so one way to do it better is to ask the gump folks to package the things we depend on directly. Means that its a little slower turnover. What does this mean concretely? That the libs we depend on will be managed at Gump? So, issue #2, would you like to ask the gump people to move our library dependencies currently in gump.xml over in the gump metadata repository instead? Don't know yet... Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research & Technology Director
Re: [PATCH][Gump] your definitions break Gump builds
Stefan Bodewig wrote: > On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > >>Stefan Bodewig wrote: >> >>>On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>>>it's not a matter of being annoyed enough (we are already!), it's >>>>the fact that cocoon needs that file at build time. >>> >>> >>>Hmm, so why don't you realize that you have a typo in it for many >>>days? Like when you rename a jar but forget to update the >>>descriptor? >> >>because cocoon doesn't use *all* of that data, only parts. > > > Unfortunately Gump gets into trouble because of the parts Cocoon > doesn't use. I know. > If you don't use any of the projects you define for jars in your repo, > maybe you better shouldn't define those projects at all? Instead nag > the Gump crew to turn them into installed packages. I personally wouldn't be against such a thing. >>>>Now, I would be totally in favor of granting the gump committers >>>>commit access to the cocoon project. >>> >>>Should be quite trivial to add a rule to asf-authorization that >>>grants rw to @gump for just that file, at least I think it allows >>>file-granularity. >> >>Even better. Can we do it or is it something that infra@ has to do? > > > Sylvain can, or I could, but I'd certainly prefer if the Coccon PMC > made the change. ok, I'll start a vote. -- Stefano.
[vote] gump-related stuff
We should try to make it easier for gump to work with us. Our build system is a little hacky in that regard since it uses partial gump information to build cocoon. Gump strongly suggests people to move their gump descriptors over to the gump repository, so that all apache committers have access to it, not just cocoon committers. This increases the ability for others to fix the problems that we might introduce. At the same time, this is not possible, since our build depends on that *and* we can't svn:externalize it because the gump metadata is not (yet!) in SVN (we could get it from viewcvs, though, but it sounds hacky) So, the easiest thing is to allow gump committers to modify our 'gump.xml' files. So, issue #1: would you like to allow this? - o - There is another issue: cocoon has unique packages that we only depend on and we place them in our gump.xml file, problem is that later on other projects might start using those and collisions might happen. Gump is not really happy when naming collisions happen (its datamodel is not namespaced, yet) so one way to do it better is to ask the gump folks to package the things we depend on directly. Means that its a little slower turnover. So, issue #2, would you like to ask the gump people to move our library dependencies currently in gump.xml over in the gump metadata repository instead? -- Stefano.
Re: [PATCH][Gump] your definitions break Gump builds
On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > Stefan Bodewig wrote: >> On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: >> >> >>>it's not a matter of being annoyed enough (we are already!), it's >>>the fact that cocoon needs that file at build time. >> >> >> Hmm, so why don't you realize that you have a typo in it for many >> days? Like when you rename a jar but forget to update the >> descriptor? > > because cocoon doesn't use *all* of that data, only parts. Unfortunately Gump gets into trouble because of the parts Cocoon doesn't use. If you don't use any of the projects you define for jars in your repo, maybe you better shouldn't define those projects at all? Instead nag the Gump crew to turn them into installed packages. >>>Now, I would be totally in favor of granting the gump committers >>>commit access to the cocoon project. >> >> Should be quite trivial to add a rule to asf-authorization that >> grants rw to @gump for just that file, at least I think it allows >> file-granularity. > > Even better. Can we do it or is it something that infra@ has to do? Sylvain can, or I could, but I'd certainly prefer if the Coccon PMC made the change. Stefan
Re: [PATCH][Gump] your definitions break Gump builds
On 17-06-2005 05:24, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: >> Should be quite trivial to add a rule to asf-authorization that grants >> rw to @gump for just that file, at least I think it allows >> file-granularity. > > Even better. Can we do it or is it something that infra@ has to do? All pmc chairs have the ability to edit the svn-authorization file in infra SVN. Other people do too (e.g. The infrastructre team). But really the request should be from the cocoon PMC to the infra@ mailing list. I'll probably end up making the changes :) LSD
Re: [PATCH][Gump] your definitions break Gump builds
Stefano Mazzocchi wrote: Stefan Bodewig wrote: On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: it's not a matter of being annoyed enough (we are already!), it's the fact that cocoon needs that file at build time. Hmm, so why don't you realize that you have a typo in it for many days? Like when you rename a jar but forget to update the descriptor? because cocoon doesn't use *all* of that data, only parts. Truth be told, cocoon could have two files, one for gump and one for its own build system, but they would contain the same information. Now, I would be totally in favor of granting the gump committers commit access to the cocoon project. Should be quite trivial to add a rule to asf-authorization that grants rw to @gump for just that file, at least I think it allows file-granularity. Even better. Can we do it or is it something that infra@ has to do? I've just tried it on a local installation of SVN, and it seems to work just fine. I believe we can just do it ourselves, although it would be polite to mention it on infra as it isn't something I've seen done before, so does establish something of a new policy. Here's the patch that would be required. It's pretty simple: Index: asf-authorization === --- asf-authorization (revision 191108) +++ asf-authorization (working copy) @@ -339,6 +339,9 @@ @cocoon = rw @lenya = rw +[/cocoon/trunk/gump.xml] [EMAIL PROTECTED] = rw + [/forrest] @forrest = rw @cocoon = rw So, we all want this? Regards, Upayavira
Re: [PATCH][Gump] your definitions break Gump builds
Sylvain Wallez wrote: Stefano Mazzocchi wrote: Now, I would be totally in favor of granting the gump committers commit access to the cocoon project. Should be quite trivial to add a rule to asf-authorization that grants rw to @gump for just that file, at least I think it allows file-granularity. Even better. Can we do it or is it something that infra@ has to do? Does the svn authorization file accept wildcards? That would allow for [**/gump.xml] @gump=rw Otherwise, each PMC is responsible for managing its own authorizations and chairs have write access to asf-authorization. From my local tests, no, wildcards don't work. So each PMC would have to add this line themselves. Upayavira
Re: [PATCH][Gump] your definitions break Gump builds
Stefano Mazzocchi wrote: Now, I would be totally in favor of granting the gump committers commit access to the cocoon project. Should be quite trivial to add a rule to asf-authorization that grants rw to @gump for just that file, at least I think it allows file-granularity. Even better. Can we do it or is it something that infra@ has to do? Does the svn authorization file accept wildcards? That would allow for [**/gump.xml] @gump=rw Otherwise, each PMC is responsible for managing its own authorizations and chairs have write access to asf-authorization. Sylvain -- Sylvain WallezAnyware Technologies http://apache.org/~sylvainhttp://anyware-tech.com Apache Software Foundation Member Research & Technology Director
Re: [PATCH][Gump] your definitions break Gump builds
On 16-06-2005 17:00, "Stefan Bodewig" <[EMAIL PROTECTED]> wrote: > On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: >> Now, I would be totally in favor of granting the gump committers >> commit access to the cocoon project. > > Should be quite trivial to add a rule to asf-authorization that grants > rw to @gump for just that file, at least I think it allows > file-granularity. Yes please. We'll add an svn:externals to gump svn if possible and all this sending patches around can go away (ooh another reason to move everything to svn!) :-) - Leo
Re: [PATCH][Gump] your definitions break Gump builds
Stefano Mazzocchi wrote: > Stefan Bodewig wrote: > > On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > > > > >>it's not a matter of being annoyed enough (we are already!), it's > >>the fact that cocoon needs that file at build time. > > > > > > Hmm, so why don't you realize that you have a typo in it for many > > days? Like when you rename a jar but forget to update the descriptor? > > because cocoon doesn't use *all* of that data, only parts. > > Truth be told, cocoon could have two files, one for gump and one for its > own build system, but they would contain the same information. > > >>Now, I would be totally in favor of granting the gump committers > >>commit access to the cocoon project. > > > > Should be quite trivial to add a rule to asf-authorization that grants > > rw to @gump for just that file, at least I think it allows > > file-granularity. > > Even better. Can we do it or is it something that infra@ has to do? PMC chairs can do it. -David
Re: [PATCH][Gump] your definitions break Gump builds
Stefan Bodewig wrote: > On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > > >>it's not a matter of being annoyed enough (we are already!), it's >>the fact that cocoon needs that file at build time. > > > Hmm, so why don't you realize that you have a typo in it for many > days? Like when you rename a jar but forget to update the descriptor? because cocoon doesn't use *all* of that data, only parts. Truth be told, cocoon could have two files, one for gump and one for its own build system, but they would contain the same information. >>Now, I would be totally in favor of granting the gump committers >>commit access to the cocoon project. > > > Should be quite trivial to add a rule to asf-authorization that grants > rw to @gump for just that file, at least I think it allows > file-granularity. Even better. Can we do it or is it something that infra@ has to do? -- Stefano.
Re: [PATCH][Gump] your definitions break Gump builds
On Thu, 16 Jun 2005, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: > it's not a matter of being annoyed enough (we are already!), it's > the fact that cocoon needs that file at build time. Hmm, so why don't you realize that you have a typo in it for many days? Like when you rename a jar but forget to update the descriptor? > Now, I would be totally in favor of granting the gump committers > commit access to the cocoon project. Should be quite trivial to add a rule to asf-authorization that grants rw to @gump for just that file, at least I think it allows file-granularity. Stefan
Re: [PATCH][Gump] your definitions break Gump builds
Le 16 juin 05, à 14:58, Stefano Mazzocchi a écrit : Now, I would be totally in favor of granting the gump committers commit access to the cocoon project... +1 -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: [PATCH][Gump] your definitions break Gump builds
Stefan Bodewig wrote: > On Thu, 16 Jun 2005, Upayavira <[EMAIL PROTECTED]> wrote: > > >>I've committed this patch to Cocoon trunk. > > > Many thanks. > > >>I presume that is the correct place. > > > Until the Cocoon project is annoyed enough by our patches and moves > the descriptor over to Gump land, I think it is. 8-) Stefan, it's not a matter of being annoyed enough (we are already!), it's the fact that cocoon needs that file at build time. Now, I would be totally in favor of granting the gump committers commit access to the cocoon project. -- Stefano.
Re: [PATCH][Gump] your definitions break Gump builds
On Thu, 16 Jun 2005, Upayavira <[EMAIL PROTECTED]> wrote: > I've committed this patch to Cocoon trunk. Many thanks. > I presume that is the correct place. Until the Cocoon project is annoyed enough by our patches and moves the descriptor over to Gump land, I think it is. 8-) Stefan
Re: [PATCH][Gump] your definitions break Gump builds
Stefan, I've committed this patch to Cocoon trunk. I presume that is the correct place. Regards, Upayavira Stefan Bodewig wrote: Hi all, your own project definitions of commons-javaflow, commons-jci and lately spring break the Gump supplied definitions. We've been building svn trunk of commons-jci for weeks now, but it gets listed as failed because it doesn't produce a jar with "your" name. spring is an installed package and has been for quite some time, even before you added a defintion. The appendend patch simply removes the three project definitions, if this is not the correct way to deal with it, please at least rename your projects. Also, in the case of jci and javaflow, this is a repeated request, see <http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111468255224092&w=2>. Please let me know if I'm not following the correct protocol here. Cheers Stefan Index: gump.xml === --- gump.xml(revision 190800) +++ gump.xml(working copy) @@ -20,7 +20,7 @@ | | $Id$ | -| see http://brutus.apache.org/gump/public/buildLog.html +| see http://vmgump.apache.org/gump/public/buildLog.html | for already existing projects | +--> @@ -1530,18 +1530,6 @@ - -org.apache.commons.javaflow - - - - - -org.apache.jci - - - - javax.jcr @@ -1553,8 +1541,4 @@ - -org.springframework - -
[PATCH][Gump] your definitions break Gump builds
Hi all, your own project definitions of commons-javaflow, commons-jci and lately spring break the Gump supplied definitions. We've been building svn trunk of commons-jci for weeks now, but it gets listed as failed because it doesn't produce a jar with "your" name. spring is an installed package and has been for quite some time, even before you added a defintion. The appendend patch simply removes the three project definitions, if this is not the correct way to deal with it, please at least rename your projects. Also, in the case of jci and javaflow, this is a repeated request, see <http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111468255224092&w=2>. Please let me know if I'm not following the correct protocol here. Cheers Stefan Index: gump.xml === --- gump.xml(revision 190800) +++ gump.xml(working copy) @@ -20,7 +20,7 @@ | | $Id$ | - | see http://brutus.apache.org/gump/public/buildLog.html + | see http://vmgump.apache.org/gump/public/buildLog.html | for already existing projects | +--> @@ -1530,18 +1530,6 @@ - -org.apache.commons.javaflow - - - - - -org.apache.jci - - - - javax.jcr @@ -1553,8 +1541,4 @@ - -org.springframework - -
[PATCH][GUMP] jci and javaflow get now built by Gump
Hi, the appendend patch will remove the project placeholders for commons-jci and commons-javaflow from your descriptor since Gump now (tries to) builds them from sources. Also I've added a dependency on commons-jci to the cocoon project since it seems to use it. I don't know enough about Excalibur Pool to help with the remaining compilation issues, sorry. Stefan Index: gump.xml === --- gump.xml(revision 165126) +++ gump.xml(working copy) @@ -73,6 +73,7 @@ + @@ -1421,16 +1422,4 @@ - -org.apache.commons.javaflow - - - - - -org.apache.jci - - - -
[GUMP@brutus]: Project cocoon (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 42 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon] -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: [cocoon-testcase] -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: [cocoon-deprecated] -DEBUG- Dependency on avalon-framework-api exists, no need to add for property avalonapi.jar. -INFO- Made directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-15042005/test] -INFO- Failed with reason build failed -INFO- Project Reports in: /usr/local/gump/public/workspace/cocoon/build/cocoon-15042005/test/output -WARNING- No directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-15042005/test/output] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html Work Name: build_cocoon_cocoon (Type: Build) Work ended in a state of : Failed Elapsed: 11 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Davalonapi.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-15042005.jar -Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-15042005.jar -Dbuild=build/cocoon-15042005 gump-core [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-15042005/classes:/usr/local/gump/public/workspace/cocoon/build/cocoon-15042005/deprecated:/usr/local/gump/public/workspace/cocoon/build/cocoon-15042005/test:/usr/local/gump/public/workspace/cocoon/build/cocoon-15042005/mocks:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/tools/loader:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/worksp
[GUMP@brutus]: Project cocoon (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 38 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon] -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: [cocoon-testcase] -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: [cocoon-deprecated] -DEBUG- Dependency on avalon-framework-api exists, no need to add for property avalonapi.jar. -INFO- Made directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-14042005/test] -INFO- Failed with reason build failed -INFO- Project Reports in: /usr/local/gump/public/workspace/cocoon/build/cocoon-14042005/test/output -WARNING- No directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-14042005/test/output] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html Work Name: build_cocoon_cocoon (Type: Build) Work ended in a state of : Failed Elapsed: 12 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Davalonapi.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-14042005.jar -Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-14042005.jar -Dbuild=build/cocoon-14042005 gump-core [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-14042005/classes:/usr/local/gump/public/workspace/cocoon/build/cocoon-14042005/deprecated:/usr/local/gump/public/workspace/cocoon/build/cocoon-14042005/test:/usr/local/gump/public/workspace/cocoon/build/cocoon-14042005/mocks:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/tools/loader:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/di
[GUMP@brutus]: Project cocoon (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 35 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon] -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: [cocoon-testcase] -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: [cocoon-deprecated] -DEBUG- Dependency on avalon-framework-api exists, no need to add for property avalonapi.jar. -INFO- Made directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-13042005/test] -INFO- Failed with reason build failed -INFO- Project Reports in: /usr/local/gump/public/workspace/cocoon/build/cocoon-13042005/test/output -WARNING- No directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-13042005/test/output] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html Work Name: build_cocoon_cocoon (Type: Build) Work ended in a state of : Failed Elapsed: 12 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Davalonapi.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-13042005.jar -Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-13042005.jar -Dbuild=build/cocoon-13042005 gump-core [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-13042005/classes:/usr/local/gump/public/workspace/cocoon/build/cocoon-13042005/deprecated:/usr/local/gump/public/workspace/cocoon/build/cocoon-13042005/test:/usr/local/gump/public/workspace/cocoon/build/cocoon-13042005/mocks:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/tools/loader:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-n
[GUMP@brutus]: Project cocoon-block-template (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-template has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-template : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [template-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/gump_work/build_cocoon_cocoon-block-template.html Work Name: build_cocoon_cocoon-block-template (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dbuild=build/cocoon-16032005 -Dblock-name=template gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/template/test:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/u
[GUMP@brutus]: Project cocoon-block-paranoid (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-paranoid has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-paranoid : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-paranoid/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [paranoid-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-paranoid/gump_work/build_cocoon_cocoon-block-paranoid.html Work Name: build_cocoon_cocoon-block-paranoid (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=paranoid gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-160
[GUMP@brutus]: Project cocoon-block-lucene (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-lucene has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-lucene : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-lucene/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [lucene-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-lucene/gump_work/build_cocoon_cocoon-block-lucene.html Work Name: build_cocoon_cocoon-block-lucene (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=lucene gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005
[GUMP@brutus]: Project cocoon-block-asciiart (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-asciiart has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-asciiart : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-asciiart/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [asciiart-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-asciiart/gump_work/build_cocoon_cocoon-block-asciiart.html Work Name: build_cocoon_cocoon-block-asciiart (Type: Build) Work ended in a state of : Failed Elapsed: 8 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=asciiart gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/asciiart/dest:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/asciiart/test:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/
[GUMP@brutus]: Project cocoon-block-proxy (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-proxy has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-proxy : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-proxy/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [proxy-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-proxy/gump_work/build_cocoon_cocoon-block-proxy.html Work Name: build_cocoon_cocoon-block-proxy (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=proxy gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/commons-httpclient-20-branch/dist/commons-httpclient-2.0-16032005.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/veloci
[GUMP@brutus]: Project cocoon-block-javaflow (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-javaflow has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-javaflow : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-javaflow/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [javaflow-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-javaflow/gump_work/build_cocoon_cocoon-block-javaflow.html Work Name: build_cocoon_cocoon-block-javaflow (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=javaflow gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/veloc
[GUMP@brutus]: Project cocoon-block-axis (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-axis has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-axis : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-axis/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [axis-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-axis/gump_work/build_cocoon_cocoon-block-axis.html Work Name: build_cocoon_cocoon-block-axis (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=axis gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-stx (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-stx has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-stx : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-stx/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [stx-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-stx/gump_work/build_cocoon_cocoon-block-stx.html Work Name: build_cocoon_cocoon-block-stx (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=stx gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/gump/pub
[GUMP@brutus]: Project cocoon-block-poi (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-poi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-poi : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-poi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [poi-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-poi/gump_work/build_cocoon_cocoon-block-poi.html Work Name: build_cocoon_cocoon-block-poi (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=poi gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/gump/pub
[GUMP@brutus]: Project cocoon-block-naming (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-naming has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-naming : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-naming/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [naming-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-naming/gump_work/build_cocoon_cocoon-block-naming.html Work Name: build_cocoon_cocoon-block-naming (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=naming gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005
[GUMP@brutus]: Project cocoon-block-jsp (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-jsp has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-jsp : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jsp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jsp-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jsp/gump_work/build_cocoon_cocoon-block-jsp.html Work Name: build_cocoon_cocoon-block-jsp (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=jsp gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/jsp/mocks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/publ
[GUMP@brutus]: Project cocoon-block-html (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-html has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-html : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-html/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [html-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-html/gump_work/build_cocoon_cocoon-block-html.html Work Name: build_cocoon_cocoon-block-html (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=html gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-deli (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-deli has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-deli : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-deli/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [deli-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-deli/gump_work/build_cocoon_cocoon-block-deli.html Work Name: build_cocoon_cocoon-block-deli (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=deli gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-bsf (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-bsf has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-bsf : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-bsf/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [bsf-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-bsf/gump_work/build_cocoon_cocoon-block-bsf.html Work Name: build_cocoon_cocoon-block-bsf (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=bsf gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/gump/pub
[GUMP@brutus]: Project cocoon-block-web3 (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-web3 has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-web3 : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-web3/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [web3-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-web3/gump_work/build_cocoon_cocoon-block-web3.html Work Name: build_cocoon_cocoon-block-web3 (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=web3 gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/web3/mocks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-template (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-template has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-template : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [template-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-template/gump_work/build_cocoon_cocoon-block-template.html Work Name: build_cocoon_cocoon-block-template (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=template gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/template/test:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/v
[GUMP@brutus]: Project cocoon-block-slop (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-slop has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-slop : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-slop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [slop-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-slop/gump_work/build_cocoon_cocoon-block-slop.html Work Name: build_cocoon_cocoon-block-slop (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=slop gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-serializers (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-serializers has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-serializers : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-serializers/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [serializers-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-serializers/gump_work/build_cocoon_cocoon-block-serializers.html Work Name: build_cocoon_cocoon-block-serializers (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=serializers gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/
[GUMP@brutus]: Project cocoon-block-qdox (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-qdox has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-qdox : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-qdox/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [qdox-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-qdox/gump_work/build_cocoon_cocoon-block-qdox.html Work Name: build_cocoon_cocoon-block-qdox (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=qdox gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-profiler (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-profiler has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-profiler : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-profiler/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [profiler-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-profiler/gump_work/build_cocoon_cocoon-block-profiler.html Work Name: build_cocoon_cocoon-block-profiler (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=profiler gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/veloc
[GUMP@brutus]: Project cocoon-block-midi (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-midi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-midi : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-midi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [midi-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-midi/gump_work/build_cocoon_cocoon-block-midi.html Work Name: build_cocoon_cocoon-block-midi (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=midi gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-velocity (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-velocity has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-velocity : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-velocity/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [velocity-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-velocity/gump_work/build_cocoon_cocoon-block-velocity.html Work Name: build_cocoon_cocoon-block-velocity (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=velocity gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/veloc
[GUMP@brutus]: Project cocoon-block-linkrewriter (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-linkrewriter has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-linkrewriter : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-linkrewriter/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [linkrewriter-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-linkrewriter/gump_work/build_cocoon_cocoon-block-linkrewriter.html Work Name: build_cocoon_cocoon-block-linkrewriter (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=linkrewriter gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/publ
[GUMP@brutus]: Project cocoon-block-jfor (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-jfor has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-jfor : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jfor/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jfor-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-jfor/gump_work/build_cocoon_cocoon-block-jfor.html Work Name: build_cocoon_cocoon-block-jfor (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=jfor gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/usr/local/g
[GUMP@brutus]: Project cocoon-block-itext (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-itext has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-itext : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-itext/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [itext-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-itext/gump_work/build_cocoon_cocoon-block-itext.html Work Name: build_cocoon_cocoon-block-itext (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=itext gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005.jar:/u
[GUMP@brutus]: Project cocoon-block-taglib (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-taglib has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-taglib : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-taglib/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [taglib-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-taglib/gump_work/build_cocoon_cocoon-block-taglib.html Work Name: build_cocoon_cocoon-block-taglib (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=taglib gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-dep-16032005
[GUMP@brutus]: Project cocoon-block-chaperon (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-chaperon has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-chaperon : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-chaperon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [chaperon-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-chaperon/gump_work/build_cocoon_cocoon-block-chaperon.html Work Name: build_cocoon_cocoon-block-chaperon (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=chaperon gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/chaperon/dest:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/blocks/chaperon/test:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/
[GUMP@brutus]: Project cocoon-block-batik (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-batik has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-batik : Java XML Framework - cocoon-block-fop : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-batik/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [batik-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-batik/gump_work/build_cocoon_cocoon-block-batik.html Work Name: build_cocoon_cocoon-block-batik (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=batik gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-16032005.jar:/usr/local/gump/public/workspace/jakarta-v
[GUMP@brutus]: Project cocoon-block-session-fw (in module cocoon) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon-block-session-fw has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-session-fw : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon/cocoon-block-session-fw/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [session-fw-block.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/cocoon/cocoon-block-session-fw/gump_work/build_cocoon_cocoon-block-session-fw.html Work Name: build_cocoon_cocoon-block-session-fw (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=16032005 -Dblock-name=session-fw gump-block [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/cocoon/tools/anttasks:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-16032005/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-16032005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-16032005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-16032005.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:/usr/local/gump/public/workspace/excalibur/components/sourceresolve/target/excalibur-sourceresolve-16032005.jar:/usr/local/gump/public/workspace/checkstyle/target/dist/checkstyle-16032005/checkstyle-16032005.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-16032005.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-16032005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/veloci
