You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/02/23 08:06:22 UTC
[jira] Updated: (SUREFIRE-126) ComponentLookupException when
running unit tests from Eclipse IDE
[ http://jira.codehaus.org/browse/SUREFIRE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-126:
----------------------------------
Fix Version/s: (was: 2.3)
2.4
> ComponentLookupException when running unit tests from Eclipse IDE
> -----------------------------------------------------------------
>
> Key: SUREFIRE-126
> URL: http://jira.codehaus.org/browse/SUREFIRE-126
> Project: Maven Surefire
> Issue Type: Bug
> Environment: Maven 2.0.4, Eclipse 3.2RC4
> Reporter: Rahul Thakur
> Fix For: 2.4
>
> Attachments: DatabaseMojoTest.java
>
>
> When I unit tests for a Mojo from within Eclipse I get the following Exception
> ---------------- snip ---------------
> org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:plexus-plugin:1.0.0-SNAPSHOT:greet.
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:222)
> at org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:164)
> at org.codehaus.plexus.m2.PlexusGreeterMojoTest.testMojoLookup(PlexusGreeterMojoTest.java:40)
> 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 junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> 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:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:457)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:670)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> ------------------- snip -------------------------
> Attached the Mojo test that was blowing up
--
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