[
http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100765
]
Max Bowsher commented on MECLIPSE-248:
--------------------------------------
Is it not *supposed* to be looking for version "test" of the plugin? - "test"
being the locally just-built version, installed into a temporary
local-repository, to be tested.
The bug (I think) is not that it looks for "test" - it is that late in one of
the tests, it re-triggers resolution of the plugin, and this time fetches a
released version from central, instead of the sandboxed test local repository.
> 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.4
>
> Attachments: log.txt,
> 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
