On 8/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 26 Aug 06, at 6:59 AM 26 Aug 06, Dennis Lundberg wrote: > > Of course, this is always an option, but it's not an ideal one. > Having to build the snapshots required to test some piece of > software takes away time from the testing itself. If the person > that wants something to be tested can provide as much as possible > up front to the persons doing the testing, then more people will > actually test it. If the dependency is sufficiently tested to > warrant a [vote] thread for the product depending on it, then a > snapshot of the dependency should be published in my opinion. > So far you are the only one who's probably even tried it. It's generally the case that the person doing the release is going solo unfortunately. So I'm glad you tried it. But I generally build everything from source, snapshots certainly can't hurt and if they help testing that's cool. Ultimately an instance of Continuum will be the arbiter. You not being able to build something doesn't mean anything either. I will start in the order I built stuff i.e. the dependency order:
If it helps I wrote up the steps I used to build internal releases of plugins (so that I can patch them until they get officially released) at http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
