On 01.04.11 06:05, Stefan Bodewig wrote: > Burn a few goats. Done. Big stench. Nothing changed. What now? ;-)
> OK, the way Gump works it means Turbine must be built before Torque, so > we must make torque-generator depend on turbine-core (and obviously > remove the torque dependencies from turbine-core). We'll also need to > check whether any of Turbine's dependencies depend on Torque themselves. > > I'll take care of this. I'm not a big fan of this solution. Such helper constructs tend to complicate things and some day nobody will remember what it was meant for in the first place. There used to be a commons-xxx-2.x dependency in Gump where some incompatible change had been circumvented. Couldn't we do the something similar here? > Secondly this means Torque 3.x will be downloaded from Maven central and > put into the local repository. Given that Torque4 seems to be known to > be incompatible to 3.x (I assume this is intentional) this may be a good It sure is. What is the general idea of Gump to handle incompatible API changes? > thing so I'd live with it (the alternative would be to use a separate > local repository). How would the local repository help here? I guess it could help me with fulcrum-quartz as well. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
