Hi!

I've runned with -U as you said, and even deleted the jar-plugin and
versions-plugin from my local repo and the same result: No mention of
jar plugin version 2.3.2.

However, if I declare it in the pluginManagement tag:

    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-jar-plugin</artifactId>
          <version>2.3.1</version>
        </plugin>
      </plugins>
    </pluginManagement>

then the versions plugin does says that there is a new 2.3.2 version.

So my guess is that the versions plugin doesn't (or cannot?) check for
plugin versions defined in the super pom.


2011/11/25 Oleg Estekhin <[email protected]>:
> Hi
>
> Under some circumstances the maven checks for new versions in the local
> repository only. Force it to check the central explicitly with
> mvn -U versions:display-plugin-updates
>
> -----Исходное сообщение----- From: Gabriel Belingueres
> Sent: Monday, November 21, 2011 6:28 PM
> To: Maven Users List
> Subject: versions plugin does not show the maven-jar-plugin 2.3.2 as a new
> version
>
> Hi!
>
> I'm using maven 3.0.3, which uses the maven-jar-plugin 2.3.1 as
> default (predefined in the super pom I think).
>
> If I run a mvn versions:display-plugin-updates then the
> maven-jar-plugin 2.3.2 does not shows in the list.
>
> Is it because I'm not explicitly declaring the use of the jar plugin
> in my pom.xml? That is, the versions plugin only works for the plugins
> I explicitly declare but not the ones in the super pom?
>
> Regards,
> Gabriel
>
> ---------------------------------------------------------------------
> 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]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to