[jira] Commented: (MECLIPSE-248) Eclipse plugin looks for pom version test
[ http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101459 ] Max Bowsher commented on MECLIPSE-248: -- This issue has become a muddle of two separate problems. Problem 1, for which I initially reported this issue, is that on some platforms/OSes/somethings, the eclipse-plugin tests failed, due to re-resolving the plugin to the latest release version, when they should have been using a locally sandbox test version. This problem is fixed, and that is reflected by this issue being Status=Closed. Problem 2, to which the comments from Carlos seem to relate, is something entirely different - a failure to execute mvn eclipse:eclipse due to resolving an incorrect version of the plugin in the first place IIRC. Please could someone with the appropriate permissions change the summary of this issue to Tests fail due to incorrectly attempting to use released plugin version, not locally sandboxed one under test, which is a brief description of problem 1. The current summary is referring to problem 2, which is not really what this issue is about. 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 Assignee: Brian Fox Priority: Blocker Fix For: 2.4 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
[jira] Commented: (MECLIPSE-248) Eclipse plugin looks for pom version test
[ http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101253 ] Brian Fox commented on MECLIPSE-248: I saw this happen to someone trying to run the eclipse plugin. It was discussed in detail on irc here: http://dev.rectang.com/logs/codehaus/%23maven/20070630.html 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, 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
[jira] Commented: (MECLIPSE-248) Eclipse plugin looks for pom version test
[ http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101254 ] Carlos Sanchez 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. No, it looks for it after it's installed and you use the plugin in your own project 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, 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
[jira] Commented: (MECLIPSE-248) Eclipse plugin looks for pom version test
[ http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101256 ] Max Bowsher commented on MECLIPSE-248: -- No, it looks for it after it's installed and you use the plugin in your own project OK. That's a different issue to the one I am reporting here, then. 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, 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
[jira] Commented: (MECLIPSE-248) Eclipse plugin looks for pom version test
[ 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
[jira] Commented: (MECLIPSE-248) Eclipse plugin looks for pom version test
[ http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100361 ] Carlos Sanchez commented on MECLIPSE-248: - the only way to get it work so far is delete the org/apache/maven/plugins/maven-eclipse-plugin folder from the local repo and install the plugin locally if you install without removing the folder doesn't work if you remove the folder and let it get downloaded doesn't work 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
[jira] Commented: (MECLIPSE-248) Eclipse plugin looks for pom version test
[ http://jira.codehaus.org/browse/MECLIPSE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100294 ] Carlos Sanchez commented on MECLIPSE-248: - If the pligin 2.4-SNAPSHOT is installed then the embedder test org.apache.maven.embedder.EmbedderUsingEclipsePluginTest also fails 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
