And for things like creating the dependency classpath? Where Ant removes non-existent files and paths? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
Lester Ward <[EMAIL PROTECTED]> wrote on 08/09/2003 11:17:58 PM: > > [EMAIL PROTECTED] wrote: > > > Yes, resolving dependencies all the time is a PITA. > > > > > > What's your suggested alternative? > > My understanding is that the problem is that the plugin manager resolves > dependencies long before any goal is executed. If that's true, I suggest the > following: > > 1) If the plugin manager cannot resolve dependencies, it does .not. > automatically fail the build. Instead, it puts the build into a "bad > dependency" state. > > 2) By default, execution of all goals first checks the "bad dependency" > state. If true, the goal fails. However... > > 3) A goal can be given an attribute that allows it to skip this check and > continue executing, even if "bad dependency" is true. Not many goals could > do this, but clean:clean could. > > --------------------------------------------------------------------- > 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]
