> As it stands, the nightly builds will use a different set of jars from the > release builds, which does not seem quite right to me.
It is debatable wether one would deem Gump builds "nightly builds" in the simple sense of them, they are more like "nightly integration tests", i.e. does a cross compile/test work. Yes, jars are produced, but because it uses the very latest (as of a certain instant) set of jars, I doubt many folks would want to test/trust them. [I could imagine a "nightly build of X" being the latest X plus the latest *release or chosen build* of all it's dependencies, purely so the X community could test out their work. Gump doesn't support that latter choice.] > Also, it we'd like to provide ready-to-run nightly builds. > > These would need to include the run-time jars, and it would be useful to be > able to package these up into a single file for download. > This is easy enough using the existing build.xml, as it already creates the > packages from the jars in the lib directory. I don't know if it is possible > to package the external jars in this way - and the build.xml would have to > skip this step if it was not running under the appropriate Gump. The above all said, there is a discussion ongoing upon [EMAIL PROTECTED] that might prove fruitful. Gump is generating a repository of jars (when allowed ,e.g. http://gump.dotnot.org/repository/) and tools ought be able to download from there. Actually, I am about to start work on Gump downloading whole trees from other Gumps, but I digress. In short, based upon my comments above, you still think that folks would want nightly build from Gump? regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
