Execution of a AbstractMojoTestCase test from within Eclipse

[Bateman, Patrick]

Sorry if I'm posting to the wrong list here.

 

I've been working on this for several days now with no solution coming
out.

 

The test works from within a Maven context, but when run it as a
stand-alone test from within Eclipse the following stack trace is
produced.

 

The Plexus look-up method prefixes the plug-in identifier with
'org.apache.maven.plugin.Mojo', and thus can't find the required
component. I understand how this works from within Maven itself, but if
run standalone, I assume the Plexus container has not yet been through
an initialisation phase.

 

Has anyone out there been trying to do a similar thing, or am I way of
the path?

 

Thanks

 

Pat

 

Maven 2.0.6 with maven-plugin-testing-harness 1.0

 

 

org.codehaus.plexus.component.repository.exception.ComponentLookupExcept
ion: Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojocom.qualcomm.uds.tools.qcgen:qcgen-maven-plu
gin:0.1:generate.

            at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:319)

            at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:436)

            at
org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:222)

            at
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(Abstract
MojoTestCase.java:172)

            at
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(Abstract
MojoTestCase.java:118)

            at
com.qualcomm.uds.tools.qcgen.maven.QCGenMojoTest.testGenerate(QCGenMojoT
est.java:30)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)

            at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)

            at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)

            at java.lang.reflect.Method.invoke(Method.java:585)

            at junit.framework.TestCase.runTest(TestCase.java:164)

            at junit.framework.TestCase.runBare(TestCase.java:130)

            at junit.framework.TestResult$1.protect(TestResult.java:110)

            at
junit.framework.TestResult.runProtected(TestResult.java:128)

            at junit.framework.TestResult.run(TestResult.java:113)

            at junit.framework.TestCase.run(TestCase.java:120)

            at junit.framework.TestSuite.runTest(TestSuite.java:228)

            at junit.framework.TestSuite.run(TestSuite.java:223)

            at
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.jav
a:35)

            at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4Tes
tReference.java:38)

            at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja
va:38)

            at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
stRunner.java:460)

            at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
stRunner.java:673)

            at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRun
ner.java:386)

            at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRu
nner.java:196)