Jason van Zyl wrote: > > Well, part of getting Maven rolling was to separate all the turbine bits > and use Maven to help with the Gump problems. All the pieces in stratum > are going to have separate builds as they will be separate components in > the commons so I will start with the mapper. > > How are we going to deal with what is a circular dep for Gump? Stratum > needs to be built before Maven can work and Stratum will need to be > built with Maven :-) I think you will have to consider Maven a binary > jar that you don't have the sources for. That's how I plan to deploy it, > as a single JAR will all that's required to work and I'm going to > slightly mangle the internal linkage (by one character so people can > debug) so that it won't interfere with anything else on the classpath.
Help with the Gump problems? EXCUSE ME? GUMP PROBLEMS? I guess I was too obtuse. There appears to be many changes that Turbine has not kept up with in commons-logger, commons-util, and other. These are NOT merely descriptor problems, but are changes made to common code that impact turbine but were apparently not made in consultation with the Turbine team. In my mind, this represents a real problem. If turbine depends on a November snapshot of commons-util and scarab were to depend on a February snapshot, and scarab were to build on Turbine, then scarab is screwed. The only solution I know of is a greater focus on backwards compatibility, and a greater degree of communication between the projects. Until those problems are addressed, gump's build of maven will continue to be held up due to prereq. I can jump up and down, scream and shout, and send daily nags. What do I get in return? A suggestion that perhaps I should decrease the frequency with which such runs are made. Grrr.... - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
