Gump _could_ use a fix version of Castor. But that's more an intend of a Continous _Build_ Server, not a Continous _Integration_ Server like Gump.
Gump should show, that a project is failing because it is not compatible with the latest version of another project. Jan >-----Ursprüngliche Nachricht----- >Von: Elliot Metsger [mailto:[EMAIL PROTECTED] >Gesendet: Donnerstag, 31. August 2006 14:57 >An: [email protected] >Betreff: Guidance on the Pluto Portal Gump build > >Hi all, > >I'm a committer the Pluto project. We're receiving Gump >reports indicating that the Pluto Portal build (for the Pluto >1.0.2 branch) is failing [0]. A change in a dependency >(Castor) is causing the build to fail. > >At this juncture, I don't think it is likely that we are going >to upgrade the 1.0.2 branch to use the latest version of >Castor, so these reports are going to continue. > >Is it feasible/appropriate/the Right Thing to modify the Gump >build to use a specific version of Castor? Is this something >that the Pluto team can take on or are the Gump configurations >managed centrally? > >All apologies if this isn't the right list for this question. > >Best Regards, >Elliot > >[0] >http://vmgump.apache.org/gump/public/portals-pluto-1.0/portals- >pluto-portal-1.0/index.html > >--------------------------------------------------------------------- >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]
