Re: [RT] The environment abstraction, part II
Upayavira wrote: > David Crossley wrote: >> Carsten Ziegeler wrote: >>> I can't speak for Daniel, but my idea/suggestion was to forget about the >>> different environments and let Cocoon always run in a servlet container. >>> The CLI would then be kind of a http client which starts up jetty and >>> then generates the site using http requests. This would simplify some >>> things in Cocoon, the question is if this would make the life of Forrest >>> too hard? >> Thanks to you all for the followup. I don't have a >> ready answer yet. Will make sure that the other >> Forrest people are aware. > > In the end, it doesn't really matter that much, and will be up to > whoever volunteers to implement the new CLI. It depends a little bit on how we see things. My opinion :) is to remove the environment abstraction completly and simply use the servlet environment while others might think that we should only base our environment abstraction on the servlet api but allow to run Cocoon in a different environment which provides *some* features of the servlet environment but not all. The difference might be subtle, but its not the same. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: TESTING.txt?
Bertrand Delacretaz schrieb: > Le 31 mars 06 à 11:06, Carsten Ziegeler a écrit : > >> As voted recently the code freeze for 2.1.9 starts *now* and hopefully >> ends with the release in one week. > > How about adding a TESTING.txt file to document which tests we run > before the release? > > We could use this to note things like "I've successfully run all > junit and htmlunit tests on macosx 10.4 with JDK1.5.2", informal > testing notes, which would stay with the release (as it's hard to > correlate testing info found elsewhere with a given release). > > If no one objects I'll create this file in the 2.1.x branch sometime > next week when I do my usual pre-release testing. Non-committers can > send their results to our lists and I'll copy them there. > Good idea, thanks Bertrand! Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: CachingSource
Jeremy Quinn wrote: > On 31 Mar 2006, at 13:08, Max Pfingsthorn wrote: > >> Core would be best as it is very general and all the cache related >> things are there as well. >> I can do it today, but what about the codefreeze? > > Whoops, bad timing Carsten, WDYT ? > Good question :) I think we should refrain from moving code during the code freeze, because it's difficult to draw the line between what is ok to be moved and what not. So the best solution is to not move things. Sorry, about that- what do others think? But the good part is that the code is in the release - it doesn't really matter where it is as long as it is available :) Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [RT] The environment abstraction, part II
David Crossley wrote: > Carsten Ziegeler wrote: >> I can't speak for Daniel, but my idea/suggestion was to forget about the >> different environments and let Cocoon always run in a servlet container. >> The CLI would then be kind of a http client which starts up jetty and >> then generates the site using http requests. This would simplify some >> things in Cocoon, the question is if this would make the life of Forrest >> too hard? > > Thanks to you all for the followup. I don't have a > ready answer yet. Will make sure that the other > Forrest people are aware. In the end, it doesn't really matter that much, and will be up to whoever volunteers to implement the new CLI. Having said that, I think it makes sense for the CLI to have its own, minimal servlet container. It could just use Jetty, but it would be better/faster if the container didn't serve over http, i.e. require an http client too. Regards, Upayavira
Re: CachingSource
* Max Pfingsthorn: > Btw, Jeremy, I don't think the caching source factory is > dependent on the eventcache block. AFAIR, it talks to the Cache > interface. Yes, I think so, see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=114361997731742&w=2 -- Jean-Baptiste Quenot http://caraldi.com/jbq/
Re: [RT] The environment abstraction, part II
El vie, 31-03-2006 a las 14:32 +1100, David Crossley escribió: > Carsten Ziegeler wrote: > > > > I can't speak for Daniel, but my idea/suggestion was to forget about the > > different environments and let Cocoon always run in a servlet container. > > The CLI would then be kind of a http client which starts up jetty and > > then generates the site using http requests. This would simplify some > > things in Cocoon, the question is if this would make the life of Forrest > > too hard? > > Thanks to you all for the followup. I don't have a > ready answer yet. Will make sure that the other > Forrest people are aware. > El mié, 29-03-2006 a las 22:54 +0200, Daniel Fagerstrom escribió: > > So the current CLI is a minimal command line Processor container, we > could have a minimal command line Servlet container instead. I do not see a problem. I guess noone has to even notice the differents. There is http://jakarta.apache.org/commons/httpclient/ I do not see a problem for forrest. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Rhino conflict
I seem to have encountered the Rhino conflict (see link) when deploying a Cocoon 2.1.7 app into BEA WebLogic: http://marc2.theaimsgroup.com/?l=xml-cocoon-dev&m=111954091902540&w=2 I've tried options 1 & 2 described there but both are causing exceptions and/or incorrect behavior in CForms (forms.js). Is this incompatibility resolved in a newer version of Cocoon? (From what I've been able to gather from the dev list it will be in the 2.2 release. Is that correct? What's an estimated date?) Could a compatible Rhino jar be dropped into a 2.1.7 app or would the app need to be upgraded? Thanks for any advice, Gary
TESTING.txt? (was: [IMP] Code freeze for 2.1.x)
Le 31 mars 06 à 11:06, Carsten Ziegeler a écrit : As voted recently the code freeze for 2.1.9 starts *now* and hopefully ends with the release in one week. How about adding a TESTING.txt file to document which tests we run before the release? We could use this to note things like "I've successfully run all junit and htmlunit tests on macosx 10.4 with JDK1.5.2", informal testing notes, which would stay with the release (as it's hard to correlate testing info found elsewhere with a given release). If no one objects I'll create this file in the 2.1.x branch sometime next week when I do my usual pre-release testing. Non-committers can send their results to our lists and I'll copy them there. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: CachingSource
On 31 Mar 2006, at 13:08, Max Pfingsthorn wrote:
Core would be best as it is very general and all the cache related
things are there as well.
I can do it today, but what about the codefreeze?
Whoops, bad timing Carsten, WDYT ?
Btw, Jeremy, I don't think the caching source factory is dependent
on the eventcache block. AFAIR, it talks to the Cache interface.
Thanks for your feedback Max.
regards Jeremy
-Original Message-
From: Reinhard Poetz [mailto:[EMAIL PROTECTED]
Sent: Friday, March 31, 2006 13:24
To: dev@cocoon.apache.org
Subject: Re: CachingSource
Jeremy Quinn wrote:
Hi All
I was wondering what happened to the CachingSource?
I used to be in the scratchpad.
Has another technique replaced this?
I am using 2.1.9-dev. I would like to force cache
(time-based) some
calls to a Webservice API, that are otherwise uncachable. I
was hoping
to do something like :
caching:cocoon:/call-the-api-blah-blah
Any suggestions ?
any takers to move the CachingSource into a block or core?
--
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
smime.p7s
Description: S/MIME cryptographic signature
RE: CachingSource
Hi!
Core would be best as it is very general and all the cache related things are
there as well.
I can do it today, but what about the codefreeze?
Btw, Jeremy, I don't think the caching source factory is dependent on the
eventcache block. AFAIR, it talks to the Cache interface.
max
> -Original Message-
> From: Reinhard Poetz [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 31, 2006 13:24
> To: dev@cocoon.apache.org
> Subject: Re: CachingSource
>
>
> Jeremy Quinn wrote:
> > Hi All
> >
> > I was wondering what happened to the CachingSource?
> >
> > I used to be in the scratchpad.
> >
> > Has another technique replaced this?
> >
> > I am using 2.1.9-dev. I would like to force cache
> (time-based) some
> > calls to a Webservice API, that are otherwise uncachable. I
> was hoping
> > to do something like :
> >
> > caching:cocoon:/call-the-api-blah-blah
> >
> > Any suggestions ?
>
> any takers to move the CachingSource into a block or core?
>
> --
> 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: CachingSource
Hi Reinhard
I think the code is dependent on eventcache, so that could be the
block to put it in, but TBH I do not know where the source has gone to.
regards Jeremy
On 31 Mar 2006, at 12:23, Reinhard Poetz wrote:
Jeremy Quinn wrote:
Hi All
I was wondering what happened to the CachingSource?
I used to be in the scratchpad.
Has another technique replaced this?
I am using 2.1.9-dev. I would like to force cache (time-based)
some calls to a Webservice API, that are otherwise uncachable. I
was hoping to do something like :
caching:cocoon:/call-the-api-blah-blah
Any suggestions ?
any takers to move the CachingSource into a block or core?
--
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
smime.p7s
Description: S/MIME cryptographic signature
Re: CachingSource
Jeremy Quinn wrote:
Hi All
I was wondering what happened to the CachingSource?
I used to be in the scratchpad.
Has another technique replaced this?
I am using 2.1.9-dev. I would like to force cache (time-based) some
calls to a Webservice API, that are otherwise uncachable. I was hoping
to do something like :
caching:cocoon:/call-the-api-blah-blah
Any suggestions ?
any takers to move the CachingSource into a block or core?
--
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
CachingSource
Hi All I was wondering what happened to the CachingSource? I used to be in the scratchpad. Has another technique replaced this? I am using 2.1.9-dev. I would like to force cache (time-based) some calls to a Webservice API, that are otherwise uncachable. I was hoping to do something like : caching:cocoon:/call-the-api-blah-blah Any suggestions ? thanks regards Jeremy smime.p7s Description: S/MIME cryptographic signature
Re: [RT] The environment abstraction, part II
David Crossley wrote: Carsten Ziegeler wrote: I can't speak for Daniel, but my idea/suggestion was to forget about the different environments and let Cocoon always run in a servlet container. The CLI would then be kind of a http client which starts up jetty and then generates the site using http requests. This would simplify some things in Cocoon, the question is if this would make the life of Forrest too hard? Thanks to you all for the followup. I don't have a ready answer yet. Will make sure that the other Forrest people are aware. Which David has done, with a post to the Forrest list - you may see a few of us post now. I've reviewed this thread, in my opinion and *only* from a Forrest perspective I feel it is unimportant how we generate the static site from Forrest. To be honest, I don't really care if we end up bundling a building/bundling a small crawler along the lines of wget in order to do the static generation (although it is great we won't need to). It looks to me like the proposals here will make life inside Cocoon much easier. This will, undoubtedly, have a knock on effect for projects like Forrest. I'm sure we will have to go through a period of pain before reaping the rewards - but I believe it will be worth it. --- Speaking in a from a wider perspective. I would ask one important question "how many other users, besides Forrest, make heavy use of the CLI and would they be damaged by this proposal?" I would *guess* this is a low number since Cocoon is a *web* framework. Ross
Re: Changes in trunk after cleanup + what else needs to be done
Daniel Fagerstrom wrote: > Agree, but a first step could be to look at the error messages. I did > that and the vast majority of errors are due to that the component > testing framework doesn't find find the role of the component. So before > deactivating all of the test it could be a good idea to see if it is > easy to make the component testing framework work again (Carsten?). Hmm, when I rewrote the core to use Spring, I think I also fixed the testing framework - but apparently not in the right way :( I'll have a look at this in the next days. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Design questions on cocoon-core
I start to study cocoon by reading the cocoon-core source code on the trunk with some UML tool's help.I find some designs confusing me, most of them are about unnecessary (duplicate) references:1. A CocoonServlet instance is associated with an instance of ServletContext and also an instance of HttpContext (implementing ServletContext interface), which also wraps the same instance of ServletContext. It seems the reference to the instance of ServletContext is not necessary. 2. A CocoonServlet instance is associated with an instance of CoreUtil, which in turns is associated with the instance of HttpContext at the first point. The association to the HttpContext seems not necessary. 3. AbstractContext implements both ServletContext and Context, but Context inherits ServletContext. So implementing ServletContext is not needed in code. 4. An instance of CoreUtil is associated with an instance of MutableSettings and an instance of BootStrapEnvironment, which in turns is associated with another instance of MutableSettings. Can these two instances of MutableSettings be combined as one? Regards,Rice
[IMP] Code freeze for 2.1.x
As voted recently the code freeze for 2.1.9 starts *now* and hopefully ends with the release in one week. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
[EMAIL PROTECTED]: Project daisy-htmlcleaner (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 daisy-htmlcleaner has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-htmlcleaner : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-htmlcleaner-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-htmlcleaner-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #25. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-htmlcleaner (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 daisy-htmlcleaner has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-htmlcleaner : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-htmlcleaner-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-htmlcleaner-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-htmlcleaner/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #25. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit-commons (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 jackrabbit-commons has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit-commons : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-commons-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-commons-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #21. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit-commons (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 jackrabbit-commons has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit-commons : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-commons-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-commons-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit-commons/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #21. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdbi (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 jdbi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdbi : Provides convenient access to relational databases using Lis... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdbi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdbi-1.3.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdbi-1.3.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdbi/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdbi/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdbi (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 jdbi has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdbi : Provides convenient access to relational databases using Lis... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdbi/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdbi-1.3.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdbi-1.3.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdbi/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdbi/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project nekodtd (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 nekodtd has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - nekodtd : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/nekodtd/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [nekodtd-0.1.11.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/nekodtd-0.1.11.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/nekodtd/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/nekodtd/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project nekodtd (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 nekodtd has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - nekodtd : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/nekodtd/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [nekodtd-0.1.11.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/nekodtd-0.1.11.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/nekodtd/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/nekodtd/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-framework (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 knopflerfish-framework has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-framework : Knopflerfish Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-framework-1.3.3.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-framework-1.3.3.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #18. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-framework (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 knopflerfish-framework has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-framework : Knopflerfish Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-framework-1.3.3.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-framework-1.3.3.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-framework/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #18. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jing (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 jing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jing : Jing performs XML Validation using RelaxNG schemas Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jing/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jing-20030619.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jing-20030619.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jing/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jing/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jing (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 jing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jing : Jing performs XML Validation using RelaxNG schemas Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jing/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jing-20030619.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jing-20030619.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jing/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jing/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
Re: Changes in trunk after cleanup + what else needs to be done
Reinhard Poetz skrev: Jorg Heymans wrote: Jorg Heymans wrote: One very important thing: Can somebody take care of the unit-tests of cocoon-core? I got 79 errors and 2 failurs. Either we throw the failing tests away or fix them. Carsten, WDYT? I'll have a look at this. oops i interpreted these test errors as compile errors , i now see that they compile fine. I'll leave the actual fixing of the tests to the better initiated :-) Deactivating them for now would be a good start ;-) Agree, but a first step could be to look at the error messages. I did that and the vast majority of errors are due to that the component testing framework doesn't find find the role of the component. So before deactivating all of the test it could be a good idea to see if it is easy to make the component testing framework work again (Carsten?). After that we could deactivate the non working tests and fix one at the time. /Daniel
[EMAIL PROTECTED]: Project joost (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 joost has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - joost : Streaming Transformation for XML (STX) library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/joost/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [joost-20040330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/joost-20040330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/joost/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/joost/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #14. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project joost (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 joost has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - joost : Streaming Transformation for XML (STX) library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/joost/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [joost-20040330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/joost-20040330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/joost/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/joost/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #14. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project garbage (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 garbage has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - garbage : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/garbage/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [apache-garbage-0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/apache-garbage-0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/garbage/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/garbage/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project garbage (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 garbage has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - garbage : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/garbage/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [apache-garbage-0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/apache-garbage-0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/garbage/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/garbage/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 jcr has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jcr : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jcr-1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jcr/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jcr/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #12. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 jcr has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jcr : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jcr-1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jcr/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jcr/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #12. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit (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 jackrabbit has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #11. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jackrabbit (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 jackrabbit has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jackrabbit : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jackrabbit-1.0-dev-r292737.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jackrabbit-1.0-dev-r292737.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jackrabbit/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #11. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 itext has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - itext : iText is a library that allows you to generate PDF files on ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-1.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/itext-1.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/itext/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/itext/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #10. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 itext has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - itext : iText is a library that allows you to generate PDF files on ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-1.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/itext-1.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/itext/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/itext/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #10. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project cowarp (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 cowarp has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cowarp : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cowarp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cowarp-0.5-dev-20051002.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/cowarp-0.5-dev-20051002.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/cowarp/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/cowarp/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #9. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project cowarp (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 cowarp has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - cowarp : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cowarp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [cowarp-0.5-dev-20051002.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/cowarp-0.5-dev-20051002.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/cowarp/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/cowarp/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #9. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 deli has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - deli : Delivery context library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-x050330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/deli-x050330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/deli/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/deli/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 deli has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - deli : Delivery context library Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-x050330.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/deli-x050330.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/deli/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/deli/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdtcore (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 jdtcore has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdtcore : Java Development Tools from the Eclipse IDE Project Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdtcore/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdtcore-3.1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdtcore-3.1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdtcore/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdtcore/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #7. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project jdtcore (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 jdtcore has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - jdtcore : Java Development Tools from the Eclipse IDE Project Full details are available at: http://vmgump.apache.org/gump/public/cocoon/jdtcore/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [jdtcore-3.1.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/jdtcore-3.1.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/jdtcore/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/jdtcore/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #7. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-util (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 daisy-util has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-util : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-util-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-util-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #6. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project daisy-util (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 daisy-util has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - daisy-util : Java XML Framework Full details are available at: http://vmgump.apache.org/gump/public/cocoon/daisy-util/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [daisy-util-1.4.1.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/daisy-util-1.4.1.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/daisy-util/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/daisy-util/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #6. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project xreporter-expression (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 xreporter-expression has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - xreporter-expression : An expression language interpreter. Full details are available at: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xreporter-expression-20040701.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/xreporter-expression-20040701.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #5. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project xreporter-expression (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 xreporter-expression has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - xreporter-expression : An expression language interpreter. Full details are available at: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [xreporter-expression-20040701.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/optional/xreporter-expression-20040701.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/optional -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/xreporter-expression/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #5. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-log (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 knopflerfish-log has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-log : Knopflerfish Log Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-log_all-1.0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-log_all-1.0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #4. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project knopflerfish-log (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 knopflerfish-log has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - knopflerfish-log : Knopflerfish Log Full details are available at: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [knopflerfish-log_all-1.0.0.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/cocoon/lib/core/knopflerfish-log_all-1.0.0.jar -ERROR- No such directory (where output is expected) : /usr/local/gump/public/workspace/cocoon/lib/core -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/knopflerfish-log/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #4. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 chaperon has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - chaperon : Chaperon is a project that helps to convert structured text ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-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 -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/chaperon/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/chaperon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #3. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
[EMAIL PROTECTED]: Project 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 chaperon has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - chaperon : Chaperon is a project that helps to convert structured text ... Full details are available at: http://vmgump.apache.org/gump/public/cocoon/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-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 -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/cocoon/chaperon/rss.xml - Atom: http://vmgump.apache.org/gump/public/cocoon/chaperon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3231032006, vmgump.apache.org:vmgump-public:3231032006 Gump E-mail Identifier (unique within run) #3. -- Apache Gump http://gump.apache.org/ [Instance: vmgump]
