works for things like the artifact, but MavenProject isn't a component and I
can't use a role lookup on it, that was my first direction where I used
components.xml for "stub" role-hint versions of things..
${basedir} works the same as before, I ended up pulling that part out and
putting it into the StubExpressionEvaluator that I made since we don't have
project instances and things to initialize the maven expression evaluator
with.
jesse
On 3/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Cool. so I was thinking we could drop all the wrapping elements to make
> it:
>
> Jesse McConnell wrote:
> > <configuration>
> > <compileSourceRoots>
> >
> >
> <compileSourceRoot>{$basedir}target/classes/unit/compiler-basic-test/src/main/java</compileSourceRoot>
> > </compileSourceRoots>
> > <compilerId>javac</compilerId>
> >
> >
> <outputDirectory>{$basedir}/target/test/unit/compiler-basic-test/target</outputDirectory>
> > <artifact implementation="
> > org.apache.maven.plugin.testing.stubs.StubArtifact"/>
> > </configuration>
>
> This raises another question:
>
> > <artifact implementation="
> > org.apache.maven.plugin.testing.stubs.StubArtifact"/>
>
> Do these have default implementations when the harness is in play?
> Trying to think if that is even possible...
>
> Having extended PlexusTestCase, you can already do that by:
>
> TestCaseName.xml:
>
> [...]
> <component>
> <role>o.a.m.a.Artifact</role>
> <implementation>o.a.m.p.t.s.StubArtifact</implemnetation>
> </component>
> [...]
>
> Not sure I really prefer that, of course. Still like to write Java
> tests, but alternatives are good :)
>
> Also, I assume its ${basedir} and you haven't changed the behaviour of
> the expression eval? :)
>
> Cheers,
> Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
jesse mcconnell
jesseDOTmcconnellATgmailDOTcom
