maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frederic Camblor <fcamb...@gmail.com>
Subject Re: Why would maven look for a newer version of a plugin?
Date Fri, 12 Nov 2010 18:16:06 GMT
<pluginManagement> is not used in <reporting> section... it is only build
section scoped.

Provide a version in your reporting plugin, and it will solve your problem
(for the moment, no version is provided for your reporting plugin, that's
why maven is gathering last plugin version from your enterprise repository).

Frédéric

On Fri, Nov 12, 2010 at 7:09 PM, Sanjeeb Sahoo <sahoo@sun.com> wrote:

> No, that snippet is part of pluginManagement. The actual usage is inside
> <reporting>, but there is no version specified at the point of use. Why
> should version be specified there if it is already present in
> pluginManagement? BTW, in case I didn't make it clear, I am looking at
> effective pom. Our project POM does not even have an entry for javadoc
> plugin under <pluginManagement>; it's inherited from SuperPOM.
>
> Sahoo
>
> On Friday 12 November 2010 08:53 PM, Frederic Camblor wrote:
>
>> 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<sahoo@sun.com>  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: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message