You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnaud Heritier (JIRA)" <ji...@codehaus.org> on 2008/03/05 15:14:28 UTC
[jira] Created: (MECLIPSE-395) Plugin tests are failing due to a
wrong local repository path.
Plugin tests are failing due to a wrong local repository path.
--------------------------------------------------------------
Key: MECLIPSE-395
URL: http://jira.codehaus.org/browse/MECLIPSE-395
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Arnaud Heritier
In a corporate environment, we have the local repository not located in the standard location (${user.home}/.m2/repository).
This is set in settings passed to maven with properties org.apache.maven.user-settings and org.apache.maven.global-settings (our settings are also not located in the standard locations ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
Instead of using my local repository defined in our global settings, eclipse integration tests are using ${user.home}/.m2/repository, thus don't find dependencies. For example :
{code}
Error getting POM for ...
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
testing.mainLocalAsRemote (file:/C:/Documents and Settings/XXXX/.m2/repository)
{code}
--
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] Reopened: (MECLIPSE-395) Plugin tests are failing due to a
wrong local repository path.
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier reopened MECLIPSE-395:
--------------------------------------
My fix breaks the build if those properties aren't set. Maven complains about '${org.apache.maven.user-settings}' references itself.
{code}
testMyEclipseProject01(org.apache.maven.plugin.eclipse.MyEclipsePluginTest) Time elapsed: 11.46 sec <<< ERROR!
org.apache.maven.shared.test.plugin.TestToolsException: Error building MavenProject instance from test pom: /Users/arnaud/Development/Maven/Code/m2-trunks/plugins/maven-eclipse-plugin/pom-test.xml
at org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:238)
at org.apache.maven.shared.test.plugin.PluginTestTool.prepareForTesting(PluginTestTool.java:181)
at org.apache.maven.shared.test.plugin.PluginTestTool.preparePluginForUnitTestingWithMavenBuilds(PluginTestTool.java:121)
at org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.setUp(AbstractEclipsePluginTestCase.java:137)
at junit.framework.TestCase.runBare(TestCase.java:128)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
Caused by: org.apache.maven.project.InvalidProjectModelException: The POM expression: ${org.apache.maven.user-settings} could not be evaluated. Reason: Expression value '${org.apache.maven.user-settings}' references itself in 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:test'. for project org.apache.maven.plugins:maven-eclipse-plugin at /Users/arnaud/Development/Maven/Code/m2-trunks/plugins/maven-eclipse-plugin/pom-test.xml
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:803)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:476)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
at org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:223)
... 24 more
Caused by: org.apache.maven.project.interpolation.ModelInterpolationException: The POM expression: ${org.apache.maven.user-settings} could not be evaluated. Reason: Expression value '${org.apache.maven.user-settings}' references itself in 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:test'.
at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolateInternal(RegexBasedModelInterpolator.java:172)
at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:98)
at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:937)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:799)
... 27 more
{code}
> Plugin tests are failing due to a wrong local repository path.
> --------------------------------------------------------------
>
> Key: MECLIPSE-395
> URL: http://jira.codehaus.org/browse/MECLIPSE-395
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Arnaud Heritier
> Assignee: Arnaud Heritier
> Fix For: 2.5
>
>
> In a corporate environment, we have the local repository not located in the standard location (${user.home}/.m2/repository).
> This is set in settings passed to maven with properties org.apache.maven.user-settings and org.apache.maven.global-settings (our settings are also not located in the standard locations ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
> Instead of using my local repository defined in our global settings, eclipse integration tests are using ${user.home}/.m2/repository, thus don't find dependencies. For example :
> {code}
> Error getting POM for ...
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> testing.mainLocalAsRemote (file:/C:/Documents and Settings/XXXX/.m2/repository)
> {code}
--
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] Updated: (MECLIPSE-395) Plugin tests are failing due to a
wrong local repository path.
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-395:
-------------------------------------
Assignee: (was: Arnaud Heritier)
> Plugin tests are failing due to a wrong local repository path.
> --------------------------------------------------------------
>
> Key: MECLIPSE-395
> URL: http://jira.codehaus.org/browse/MECLIPSE-395
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Arnaud Heritier
>
> In a corporate environment, we have the local repository not located in the standard location (${user.home}/.m2/repository).
> This is set in settings passed to maven with properties org.apache.maven.user-settings and org.apache.maven.global-settings (our settings are also not located in the standard locations ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
> Instead of using my local repository defined in our global settings, eclipse integration tests are using ${user.home}/.m2/repository, thus don't find dependencies. For example :
> {code}
> Error getting POM for ...
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> testing.mainLocalAsRemote (file:/C:/Documents and Settings/XXXX/.m2/repository)
> {code}
--
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] Updated: (MECLIPSE-395) Plugin tests are failing due to a
wrong local repository path.
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-395:
-------------------------------------
Fix Version/s: (was: 2.5)
> Plugin tests are failing due to a wrong local repository path.
> --------------------------------------------------------------
>
> Key: MECLIPSE-395
> URL: http://jira.codehaus.org/browse/MECLIPSE-395
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Arnaud Heritier
> Assignee: Arnaud Heritier
>
> In a corporate environment, we have the local repository not located in the standard location (${user.home}/.m2/repository).
> This is set in settings passed to maven with properties org.apache.maven.user-settings and org.apache.maven.global-settings (our settings are also not located in the standard locations ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
> Instead of using my local repository defined in our global settings, eclipse integration tests are using ${user.home}/.m2/repository, thus don't find dependencies. For example :
> {code}
> Error getting POM for ...
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> testing.mainLocalAsRemote (file:/C:/Documents and Settings/XXXX/.m2/repository)
> {code}
--
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] Issue Comment Edited: (MECLIPSE-395) Plugin tests are
failing due to a wrong local repository path.
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=126609#action_126609 ]
aheritier edited comment on MECLIPSE-395 at 9/2/08 6:25 PM:
------------------------------------------------------------------
My fix breaks the build if those properties aren't set. Maven complains about '$/{org.apache.maven.user-settings/}' references itself.
{code}
testMyEclipseProject01(org.apache.maven.plugin.eclipse.MyEclipsePluginTest) Time elapsed: 11.46 sec <<< ERROR!
org.apache.maven.shared.test.plugin.TestToolsException: Error building MavenProject instance from test pom: /Users/arnaud/Development/Maven/Code/m2-trunks/plugins/maven-eclipse-plugin/pom-test.xml
at org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:238)
at org.apache.maven.shared.test.plugin.PluginTestTool.prepareForTesting(PluginTestTool.java:181)
at org.apache.maven.shared.test.plugin.PluginTestTool.preparePluginForUnitTestingWithMavenBuilds(PluginTestTool.java:121)
at org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.setUp(AbstractEclipsePluginTestCase.java:137)
at junit.framework.TestCase.runBare(TestCase.java:128)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
Caused by: org.apache.maven.project.InvalidProjectModelException: The POM expression: ${org.apache.maven.user-settings} could not be evaluated. Reason: Expression value '${org.apache.maven.user-settings}' references itself in 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:test'. for project org.apache.maven.plugins:maven-eclipse-plugin at /Users/arnaud/Development/Maven/Code/m2-trunks/plugins/maven-eclipse-plugin/pom-test.xml
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:803)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:476)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
at org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:223)
... 24 more
Caused by: org.apache.maven.project.interpolation.ModelInterpolationException: The POM expression: ${org.apache.maven.user-settings} could not be evaluated. Reason: Expression value '${org.apache.maven.user-settings}' references itself in 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:test'.
at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolateInternal(RegexBasedModelInterpolator.java:172)
at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:98)
at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:937)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:799)
... 27 more
{code}
was (Author: aheritier):
My fix breaks the build if those properties aren't set. Maven complains about '${org.apache.maven.user-settings}' references itself.
{code}
testMyEclipseProject01(org.apache.maven.plugin.eclipse.MyEclipsePluginTest) Time elapsed: 11.46 sec <<< ERROR!
org.apache.maven.shared.test.plugin.TestToolsException: Error building MavenProject instance from test pom: /Users/arnaud/Development/Maven/Code/m2-trunks/plugins/maven-eclipse-plugin/pom-test.xml
at org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:238)
at org.apache.maven.shared.test.plugin.PluginTestTool.prepareForTesting(PluginTestTool.java:181)
at org.apache.maven.shared.test.plugin.PluginTestTool.preparePluginForUnitTestingWithMavenBuilds(PluginTestTool.java:121)
at org.apache.maven.plugin.eclipse.AbstractEclipsePluginTestCase.setUp(AbstractEclipsePluginTestCase.java:137)
at junit.framework.TestCase.runBare(TestCase.java:128)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
Caused by: org.apache.maven.project.InvalidProjectModelException: The POM expression: ${org.apache.maven.user-settings} could not be evaluated. Reason: Expression value '${org.apache.maven.user-settings}' references itself in 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:test'. for project org.apache.maven.plugins:maven-eclipse-plugin at /Users/arnaud/Development/Maven/Code/m2-trunks/plugins/maven-eclipse-plugin/pom-test.xml
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:803)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:476)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
at org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:223)
... 24 more
Caused by: org.apache.maven.project.interpolation.ModelInterpolationException: The POM expression: ${org.apache.maven.user-settings} could not be evaluated. Reason: Expression value '${org.apache.maven.user-settings}' references itself in 'org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:test'.
at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolateInternal(RegexBasedModelInterpolator.java:172)
at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.interpolate(RegexBasedModelInterpolator.java:98)
at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:937)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:799)
... 27 more
{code}
> Plugin tests are failing due to a wrong local repository path.
> --------------------------------------------------------------
>
> Key: MECLIPSE-395
> URL: http://jira.codehaus.org/browse/MECLIPSE-395
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Arnaud Heritier
> Assignee: Arnaud Heritier
>
> In a corporate environment, we have the local repository not located in the standard location (${user.home}/.m2/repository).
> This is set in settings passed to maven with properties org.apache.maven.user-settings and org.apache.maven.global-settings (our settings are also not located in the standard locations ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
> Instead of using my local repository defined in our global settings, eclipse integration tests are using ${user.home}/.m2/repository, thus don't find dependencies. For example :
> {code}
> Error getting POM for ...
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> testing.mainLocalAsRemote (file:/C:/Documents and Settings/XXXX/.m2/repository)
> {code}
--
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] Closed: (MECLIPSE-395) Plugin tests are failing due to a
wrong local repository path.
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier closed MECLIPSE-395.
------------------------------------
Assignee: Arnaud Heritier
Resolution: Fixed
Fix Version/s: 2.5
Fixed by passing new properties in surefire (org.apache.maven.global-settings and org.apache.maven.user-settings)
> Plugin tests are failing due to a wrong local repository path.
> --------------------------------------------------------------
>
> Key: MECLIPSE-395
> URL: http://jira.codehaus.org/browse/MECLIPSE-395
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Arnaud Heritier
> Assignee: Arnaud Heritier
> Fix For: 2.5
>
>
> In a corporate environment, we have the local repository not located in the standard location (${user.home}/.m2/repository).
> This is set in settings passed to maven with properties org.apache.maven.user-settings and org.apache.maven.global-settings (our settings are also not located in the standard locations ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
> Instead of using my local repository defined in our global settings, eclipse integration tests are using ${user.home}/.m2/repository, thus don't find dependencies. For example :
> {code}
> Error getting POM for ...
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> testing.mainLocalAsRemote (file:/C:/Documents and Settings/XXXX/.m2/repository)
> {code}
--
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