Hi, Is your snippet extracted from the <build> or the <reporting> pom section ?
Check that your version is provided on both of these sections (even if you provided it in /project/build/pluginManagement) Frédéric On Fri, Nov 12, 2010 at 3:29 PM, Sanjeeb Sahoo <[email protected]> wrote: > I would like someone to help us understand a behavior that we recently > observed in our build system. In our project POM, we don't explicitly > mention the versions for these plugins, as we expect the versions to be > inherited from SuperPOM. When I look at the effective POM for the project, > it shows the following configuration for javadoc plugin: > > <plugin> > <artifactId>maven-javadoc-plugin</artifactId> > <version>2.5</version> > </plugin> > > yet, when I try to build (I am using maven 2.2.1), I get this error: > > [INFO] [ERROR] BUILD FAILURE > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] A required plugin was not found: Plugin could not be found - > check that the goal name is correct: Unable to download the artifact from > any repository > [INFO] > [INFO] Try downloading the file manually from the project website. > [INFO] > [INFO] Then, install it using the command: > [INFO] mvn install:install-file -DgroupId=org.apache.maven.plugins > -DartifactId=maven-javadoc-plugin -Dversion=2.8-SNAPSHOT > -Dpackaging=maven-plugin -Dfile=/path/to/file > [INFO] > [INFO] Alternatively, if you host your own repository you can deploy the > file there: > [INFO] mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins > -DartifactId=maven-javadoc-plugin -Dversion=2.8-SNAPSHOT > -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > [INFO] > [INFO] > [INFO] > org.apache.maven.plugins:maven-javadoc-plugin:maven-plugin:2.8-SNAPSHOT > [INFO] > [INFO] from the specified remote repositories: > [INFO] central (http://repo1.maven.org/maven2), > [INFO] glassfish-maven-repository ( > http://maven.glassfish.org/content/groups/glassfish-group/) > > We started seeing this after the maven-metadata in our nexus repo, which is > configured to proxy only released artifacts, got updated with SNAPSHOT > artifact details. The nexus repo issue has been fixed after upgrading to > 1.8.0, but what is not understood is why maven even attempted to use > 2.8-SNAPSHOT when effective pom shows the plugin version as 2.5. > > Thanks, > Sahoo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
