You can alternatively try "maven -cpu install" to force a plugin update check
On Jan 2, 2008 3:07 PM, Evan Worley <[EMAIL PROTECTED]> wrote: > Dmitry, > > Try changing the update policy in your pluginRepository to "always". I am > not positive how this policy works with respect to resolving new plugins (as > opposed to updating an existing), but might be worth a try. > > -Evan > > > On Jan 2, 2008 3:01 PM, Dmitry Beransky <[EMAIL PROTECTED]> wrote: > > > On Jan 2, 2008 2:49 PM, Evan Worley <[EMAIL PROTECTED]> wrote: > > > Can you attach your entire <repositories> and <pluginRepositories> > > entries from your pom? > > > > Hey Evan, > > > > Here they are, copied directly from help:effective-pom's output: > > > > <repositories> > > <repository> > > <id>csa-internal</id> > > <name>CSA Maven 2 Repository</name> > > <url>http://newzealand/repository/maven2</url> > > </repository> > > <repository> > > <snapshots> > > <enabled>false</enabled> > > </snapshots> > > <id>central</id> > > <name>Maven Repository Switchboard</name> > > <url>http://repo1.maven.org/maven2 </url> > > </repository> > > </repositories> > > <pluginRepositories> > > <pluginRepository> > > <releases> > > <updatePolicy>never</updatePolicy> > > </releases> > > <snapshots> > > <enabled>false</enabled> > > </snapshots> > > <id>central</id> > > <name>Maven Plugin Repository</name> > > <url>http://repo1.maven.org/maven2</url> > > </pluginRepository> > > </pluginRepositories> > > > > > > Thanks > > Dmitry > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
