Maven 2.x Help Plugin

mvn help:describe returns the version that is specified in metadata instead of the one in the parent pom

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0.1
  • Fix Version/s: Backlog
  • Component/s: describe
  • Labels:
    None
  • Environment:
    windows xp
    tested with mvn 2.0.8 & 2.0.9
  • Number of attachments :
    0

Description

mvn help:describe returns a different version than mvn help:effective-pom returns:

> mvn help:describe -Dplugin=surefire

...
[INFO] [help:describe]
[INFO] Plugin: 'org.apache.maven.plugins:maven-surefire-plugin:2.2'
-----------------------------------------------
Group Id:  org.apache.maven.plugins
Artifact Id: maven-surefire-plugin
Version:     2.2
Goal Prefix: surefire

However, when I run mvn help:effective-pom

I get

...
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.4.3</version>
          <configuration>
            <testFailureIgnore>true</testFailureIgnore>
            <includes>
              <include>**/*Test.java</include>
            </includes>
            <format>html</format>
          </configuration>
        </plugin>
      </plugins>
    </pluginManagement>
...

My pom structure is quite simple: just a parent pom.xml with the pluginmanagement section as above and a child pom using that. I have tested with both maven 2.0.8 and 2.0.9.

See the discussion here: http://www.nabble.com/Wrong-output-of-mvn-help%3Adescribe--td19168212.html

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ha Ryon added a comment -

Same with Maven 2.1.0.

In <pluginManagement> of a Corporate Pom I use javadoc plugin 2.3, while latest is 2.5.
effective-pom returns 2.3. describe returns 2.5.

I don't think it's a bug. I think help:describe just describe the latest version.

When I type : mvn help:describe -Dplugin=org.apache.maven.plugins:maven-javadoc-plugin
I'm using a "artifact identifier" syntax which usually includes version (which I skipped). And I guess "LATEST" is used when I do not give explicit version.

It looks like to me that help:describe doesn't read pom.xml at all (except for repository locations?). It only operates on repository. right ?

Show
Ha Ryon added a comment - Same with Maven 2.1.0. In <pluginManagement> of a Corporate Pom I use javadoc plugin 2.3, while latest is 2.5. effective-pom returns 2.3. describe returns 2.5. I don't think it's a bug. I think help:describe just describe the latest version. When I type : mvn help:describe -Dplugin=org.apache.maven.plugins:maven-javadoc-plugin I'm using a "artifact identifier" syntax which usually includes version (which I skipped). And I guess "LATEST" is used when I do not give explicit version. It looks like to me that help:describe doesn't read pom.xml at all (except for repository locations?). It only operates on repository. right ?
Hide
Permalink
Keith David Winkler added a comment -

Still happens in version 2.2.1

Effective pom specifies resources plugin 2.3

"mvn help:describe -Dplugin=resources" downloads and lists help for version 2.4.1

In any case this FAQ entry seems wrong: http://maven.apache.org/general.html#plugin-version

Show
Keith David Winkler added a comment - Still happens in version 2.2.1 Effective pom specifies resources plugin 2.3 "mvn help:describe -Dplugin=resources" downloads and lists help for version 2.4.1 In any case this FAQ entry seems wrong: http://maven.apache.org/general.html#plugin-version
Hide
Permalink
Brett Porter added a comment -

Adding the plugin to your build works around this:

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
</plugin>
</plugins>
</build>

Implicit ones don't work. I think this should be fixed in 3.0-alpha, but I'm noticing a further regression that it reports the latest release in both cases. This will need further investigation about where the cause is.

Show
Brett Porter added a comment - Adding the plugin to your build works around this: <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> </plugin> </plugins> </build> Implicit ones don't work. I think this should be fixed in 3.0-alpha, but I'm noticing a further regression that it reports the latest release in both cases. This will need further investigation about where the cause is.
Brett Porter made changes -
Field Original Value New Value
Fix Version/s Backlog [ 16303 ]
Robert Scholte made changes -
Description mvn help:describe returns a different version than mvn help:effective-pom returns:

> mvn help:describe -Dplugin=surefire

...
[INFO] [help:describe]
[INFO] Plugin: 'org.apache.maven.plugins:maven-surefire-plugin:2.2'
-----------------------------------------------
Group Id: org.apache.maven.plugins
Artifact Id: maven-surefire-plugin
Version: 2.2
Goal Prefix: surefire

However, when I run:
> mvn help:effective-pom

I get
...
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.4.3</version>
          <configuration>
            <testFailureIgnore>true</testFailureIgnore>
            <includes>
              <include>**/*Test.java</include>
            </includes>
            <format>html</format>
          </configuration>
        </plugin>
      </plugins>
    </pluginManagement>
...


My pom structure is quite simple: just a parent pom.xml with the pluginmanagement section as above and a child pom using that. I have tested with both maven 2.0.8 and 2.0.9.

See the discussion here: http://www.nabble.com/Wrong-output-of-mvn-help%3Adescribe--td19168212.html 		{{mvn help:describe}} returns a different version than {{mvn help:effective-pom}} returns:

{noformat}
> mvn help:describe -Dplugin=surefire

...
[INFO] [help:describe]
[INFO] Plugin: 'org.apache.maven.plugins:maven-surefire-plugin:2.2'
-----------------------------------------------
Group Id: org.apache.maven.plugins
Artifact Id: maven-surefire-plugin
Version: 2.2
Goal Prefix: surefire
{noformat}

However, when I run {{mvn help:effective-pom}}

I get
{code:xml}
...
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.4.3</version>
          <configuration>
            <testFailureIgnore>true</testFailureIgnore>
            <includes>
              <include>**/*Test.java</include>
            </includes>
            <format>html</format>
          </configuration>
        </plugin>
      </plugins>
    </pluginManagement>
...
{code}

My pom structure is quite simple: just a parent {{pom.xml}} with the pluginmanagement section as above and a child pom using that. I have tested with both maven 2.0.8 and 2.0.9.

See the discussion here: http://www.nabble.com/Wrong-output-of-mvn-help%3Adescribe--td19168212.html
Component/s describe [ 15787 ]
Hide
Permalink
Robert Scholte added a comment -

I've found a problem for M3.0.4:

org.apache.maven.plugin.internal.DefaultPluginManager.verifyPlugin(Plugin, MavenProject, Settings, ArtifactRepository)
...
        if ( plugin.getVersion() == null )
        {
            PluginVersionRequest versionRequest =
                new DefaultPluginVersionRequest( plugin, session.getRepositorySession(),
                                                 project.getRemotePluginRepositories() );
            plugin.setVersion( pluginVersionResolver.resolve( versionRequest ).getVersion() );
        }
...

The Model is not passed to the versionRequest, so the version is resolved based on repositories.

There's no clear description of what the verifyPlugin() should do, so it's hard to tell if we can just add the Model.

Show
Robert Scholte added a comment - I've found a problem for M3.0.4: org.apache.maven.plugin.internal.DefaultPluginManager.verifyPlugin(Plugin, MavenProject, Settings, ArtifactRepository) ... if ( plugin.getVersion() == null ) { PluginVersionRequest versionRequest = new DefaultPluginVersionRequest( plugin, session.getRepositorySession(), project.getRemotePluginRepositories() ); plugin.setVersion( pluginVersionResolver.resolve( versionRequest ).getVersion() ); } ... The Model is not passed to the versionRequest , so the version is resolved based on repositories. There's no clear description of what the verifyPlugin() should do, so it's hard to tell if we can just add the Model .

People

  • Assignee:
    Unassigned
    Reporter:
    Rintcius Blok
Vote (2)
Watch (3)

Dates

  • Created:
    Updated: