[jira] Updated: (MECLIPSE-248) Eclipse plugin looks for pom version "test"

["Max Bowsher (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Bowsher updated MECLIPSE-248:
---------------------------------

    Attachment: MECLIPSE-248.patch

It turns out that this issue is simply because there are

{code:xml}
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-eclipse-plugin</artifactId>
        <configuration>
          .......
        </configuration>
      </plugin>
    </plugins>
  </build>
{code}

blocks in a few of the test pom.xml files that fail to specify a version.

The result is that one plugin version is designated on the command line, and a different one in the pom.xml. 

To be precise, there are 38 <plugin> blocks for the maven-eclipse-plugin in the test pom.xml files, of which 35 specify <version>test</version> and 3 do not.

Fixing up those 3 to be consistent with the other 35 solves the issue.




> Eclipse plugin looks for pom version "test"
> -------------------------------------------
>
>                 Key: MECLIPSE-248
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-248
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3, 2.4
>         Environment: Linux (Ubuntu Edgy), Maven 2.0.5, JDK5update11, totally empty local repository, no remote repositories other than central
>            Reporter: Max Bowsher
>            Priority: Blocker
>             Fix For: 2.5
>
>         Attachments: log.txt, MECLIPSE-248.patch, org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest_testModule1Project.build.log
>
>
> A clean build of the maven-eclipse-plugin-2.3 tag fails, because of a test failure:
> Tests in error: 
>   testModule1Project(org.apache.maven.plugin.eclipse.EclipsePluginMasterProjectTest)
> (build log for this test is attached)
> Presumably this is not the fault of the eclipse plugin code, since it must have built at one time in order to be released, but I'm not sure where else to report it.
> The test failure poses a problem for people trying to make modified versions of the plugin based on the last released version.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira