Yes, resolving dependencies all the time is a PITA.
What's your suggested alternative?
Do plugins declare whether they need the dependencies?
Some other method of us guessing?
news <[EMAIL PROTECTED]> wrote on 06/09/2003 02:35:48 AM:
> For things like "maven clean" resolving the project's
> dependencies seems like overkill. For example, while I am
> working with my plugin for GUIApp and makeing things generally
> usable, I have to have a snapshot of some of its dependencies
> just to clean the target directory. If I don't have those
> snapshots, then I am SOL. The clean fails.
>
> Sure there is a workaround ("rm -rf target"), but it is
> a PITA to have to deal with--especially when I need to purge
> the snapshots out of my repository. I.e. the plugin is affecting
> the builds, so I want to make sure only good builds are in the
> repository.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
