RE: more on gump
Thanks to some help from Adam we we're getting real close now: Successful builds: 128 Build failures: 1 Prerequisite failures:8 The single build failure is related to the avalon-http-examples project due to a FileNotFoundException: avalon/http/blocks/avalon-http-servlet-26082004.block. Looking at the avalon-http-servlet build I can see that the servlet block has been created and installed - so I'm a little confused (again) but I'll dig around and see what comes up. Stephen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more on gump
> -Original Message- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: 26 August 2004 07:10 > To: 'Avalon Developers List' > Cc: [EMAIL PROTECTED] > Subject: RE: more on gump > > > > > -Original Message- > > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > Sent: 24 August 2004 05:08 > > To: 'Avalon Developers List' > > Cc: [EMAIL PROTECTED] > > Subject: RE: more on gump > > > > > > Current status of the Avalon Gump builds: > > > > Successful builds: 98 > > Build failures: 9 > > Prerequisite failures: 30 > > > Thinks are getting closer to total success: > > Successful builds: 116 > Build failures: 3 > Prerequisite failures: 18 > > Of the three failures, one is related to the site generation which for > the moment I simply have not figured out. The second is an issue > related to the version of JMX (using MX4J libs) - Gump is linked to > version 2 and Avalon JMX facilities are linked to 1.1 (Cameron is > digging into this as we speak - i.e. expect synchronization shortly). Cameron has just committed updates to jmx that should in principal resolve the current jmx/mx4j builds (and resolve at least 2 of out our 18 prerequisite failures). We should have confirmation from Gump in around two or three hours. Cheers, Stephen. > The third item is the http implementation which requires the addition of > the org.mortbay.jaas.jar file by the Gump team (Gump guys .. we need > your help on this one). > > Cheers, Steve. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more on gump
> -Original Message- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: 24 August 2004 05:08 > To: 'Avalon Developers List' > Cc: [EMAIL PROTECTED] > Subject: RE: more on gump > > > Current status of the Avalon Gump builds: > > Successful builds: 98 > Build failures: 9 > Prerequisite failures: 30 Thinks are getting closer to total success: Successful builds: 116 Build failures: 3 Prerequisite failures: 18 Of the three failures, one is related to the site generation which for the moment I simply have not figured out. The second is an issue related to the version of JMX (using MX4J libs) - Gump is linked to version 2 and Avalon JMX facilities are linked to 1.1 (Cameron is digging into this as we speak - i.e. expect synchronization shortly). The third item is the http implementation which requires the addition of the org.mortbay.jaas.jar file by the Gump team (Gump guys .. we need your help on this one). Cheers, Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more on gump
Current status of the Avalon Gump builds: Successful builds: 98 Build failures: 9 Prerequisite failures: 30 The build failures are related to two items: 1. getting the jetty jaas libraries into gump 2. a bug in the meta-info generator task (patches by Tim a few minutes ago) The prerequisite failures are linked to: 1. internal failures described above. 2. Excalibur build failures. Should have a clean picture on all of this in a two or three hours. Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more on gump
> -Original Message- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: 22 August 2004 21:05 > To: 'Gump code and data' > Subject: RE: more on gump > > > > Ummm - I'm a little lost - > >... all Avalon projects are failing with the assertion that build.xml > does not exist. That's a little odd because it exists in svn and the ant > basedirs are all correct. Can anyone check if there were any problems > with gump's svn checkout of the Avalon-svn repository content? p.s. on this page: http://brutus.apache.org/gump/public/avalon/index.html There is this note: Error *** Failed to update from source control. Stale contents *** And this following link: http://brutus.apache.org/gump/public/avalon/gump_work/update_avalon.html shows an output message of: svn: 'avalon' is not a working copy Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more on gump
Ummm - I'm a little lost - ... all Avalon projects are failing with the assertion that build.xml does not exist. That's a little odd because it exists in svn and the ant basedirs are all correct. Can anyone check if there were any problems with gump's svn checkout of the Avalon-svn repository content? Steve. > -Original Message- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: 22 August 2004 17:29 > To: Avalon Developers List > Cc: [EMAIL PROTECTED] > Subject: more on gump > > > I have just replaced all of the avalon/trunk gump project descriptors so > that they now point to svn content as opposed to cvs. > > I am expecting some errors related to project id to gump id names > mappings and will sort these out as they come up. All of the new gump > project definitions (138 in total) are using magic to build the > respective targets based on generated definitions - so if something goes > wrong we should be updating information in either magic's gump task or > more probably gump alias declarations in our local index files. > > Steve. > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: more on gump -- cocoon def
Could someone please update the cocoon-2.1/cocoon gump descriptor and replace the following line: with: Cheers, Steve. > -Original Message- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: 22 August 2004 17:29 > To: Avalon Developers List > Cc: [EMAIL PROTECTED] > Subject: more on gump > > > I have just replaced all of the avalon/trunk gump project descriptors so > that they now point to svn content as opposed to cvs. > > I am expecting some errors related to project id to gump id names > mappings and will sort these out as they come up. All of the new gump > project definitions (138 in total) are using magic to build the > respective targets based on generated definitions - so if something goes > wrong we should be updating information in either magic's gump task or > more probably gump alias declarations in our local index files. > > Steve. > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
