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 end up with multiple versions when they
> change.
> > The recent code changes I've made that are currently 
> uncommitted will
> only
> > load the plugins present in $MAVEN_HOME, regardless of what 
> versions 
> > are
> in
> > the cache (although it stil extracts them to the local cache).
> 
> Huh?
> 
>     <j:if test="${downloaded}">
>       <echo>Plugin downloaded, removing other versions</echo>
> 
>       <delete verbose="false">
>         <fileset dir="${maven.home}/plugins">
>           <include name="${artifactId}-*.jar" />
>           <exclude name="${artifactId}-${version}.jar" />
>         </fileset>
>       </delete>
> 
>       <delete includeEmptyDirs="true" verbose="false">
>         <fileset dir="${maven.plugin.unpacked.dir}">
>           <include name="*.cache"/>
>           <include name="**/.processed" />
>           <include name="${artifactId}-*/**" />
>         </fileset>
>       </delete>
>     </j:if>
> 
> Should do it, right?
> 
> The above is in the plugin.
> --
> dIon Gillard, Multitask Consulting
> Blog:      http://blogs.codehaus.org/people/dion/
> Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to