I've had a similar problem. It appears that Maven is able to download the pom for a plugin but not the plugin itself if you don't have <pluginRepositories> defined but do have <repositories>. If you clear everything from your local repo then attempt to download the plugin as a side-effect of your build you'll see the repo directory created and the correct pom pulled down to that directory. Maven will then fail saying that it can't find the jar. You'll see a message saying that Maven is trying to load the jar from a different repository from the one in which it found the pom (usually "central").
I found this problem with plugins I had written myself. It might also be something you'll see with external plugins.... Kevan. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 13, 2007 4:02 PM To: Maven Users List Subject: Re: Maven 2 can't find plugins Without knowing anything more about your project or seeing your pom.xml files, I assume you've declared <repositories> but not <pluginRepositories> to match. Wayne On 2/13/07, Rod Mclaughlin <[EMAIL PROTECTED]> wrote: > I have an even more basic issue. Whenever I have a plugin in a POM.xml > file, and try to use it, eg. > *$ mvn xfire:wsdlgen * > Maven 2 says* > 'Scanning for projects... Searching repository for plugin with prefix: > 'xfire'. org.apache.maven.plugins: checking for updates > org.codehaus.mojo: checking for updates from central artifact > org.apache.maven.plugins:maven-xfire-plugin: checking for updates from > central > [ERROR] BUILD ERROR > The plugin 'org.apache.maven.plugins:maven-xfire-plugin' does not exist > or no valid version could be found'* > This is true whatever the plugin. It's not a proxy issue: it can > download ordinary jars from the repository, just not plugins. For > example, here is a simple bit of a POM referring to xfire-maven-plugin: > <build> > <pluginManagement> > <plugins> > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>xfire-maven-plugin</artifactId> > <executions> > <execution> > <phase>test-compile</phase> > <goals> > <goal>wsdlgen</goal> > </goals> > </execution> > </executions> > <!-- this shows the default --> > <configuration> > > <outputDirectory>${project.build.directory}/generated-sources/xfire/wsdl gen</outputDirectory> > <configs> > > <wsdl>${basedir}/src/main/resources/META-INF/xfire/services.xml</wsdl> > </configs> > </configuration> > > </plugin> > > </plugins> > </pluginManagement> > </build> > > > Again, I've searched the web, the mailing lists etc.. Thanks for any > advice... > > > > --------------------------------------------------------------------- > 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] This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information that is protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
