Ah, gotcha!
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Brett Porter <[EMAIL PROTECTED]> wrote on 29/10/2003 10:10:34 AM:
> As I said, it doesn't clear "every" user's local cache. It'll only
> Any way to make it automatically download the latest? Or
> would that be a snapshot?
>
Exactly.
It won't go out to the internet to get them unless they are listed in
maven.repo.remote.
- Brett
As I said, it doesn't clear "every" user's local cache. It'll only clear the
executing user, which isn't very helpful in a multi-user environment. Same
deal with plugin:install.
- Brett
> > The downside of plugin:download is that it doesn't clear out every
> user's
> > local plugin cache, so they
> > I've successfully setup an in-house remote repository along with a
> > central Maven distribution provided via our source control
> system. At
> > this time, I can update a jar in the maven distribution's plugin
> > folder, and then when someone runs a build, they'll get the latest
> > ve
Brett Porter <[EMAIL PROTECTED]> wrote on 29/10/2003 09:12:31 AM:
> The downside of plugin:download is that it doesn't clear out every
user's
> local plugin cache, so they end up with multiple versions when they
change.
> The recent code changes I've made that are currently uncommitted will
onl
> I've successfully setup an in-house remote repository along
> with a central Maven distribution provided via our source
> control system. At this time, I can update a jar in the
> maven distribution's plugin folder, and then when someone
> runs a build, they'll get the latest version install
