Sorry... I meant Mark!
Mark, let me know if you want me to submit a patch.
Randy
Randy Watler wrote:
Adam,
After rereading Matt's question and your original problem report, I
believe you are asking how to get the target/test-classes directory
within a single project added to the class path used to invoke the
enhancer. By default, the existing target/classes directory is
included, but not target/test-classes.
I believe that we could add a new tag/mojo list member called
"additionalClasspathElements". AFAICT, that is the conventional
approach to this. We could also add a mojo member for
testClasspathElements and use those if available... i.e. in the
process-test-classes phase.
Matt... do you want me to submit a patch with either change, or do you
want to handle this?
Randy
Randy Watler wrote:
Adam,
I stand corrected. Let me take a look for you.
Randy
Adam Hardy wrote:
Randy Watler on 04/03/09 14:28, wrote:
Just to clarify.... this is also using version 1.0 of the plugin? I
dont think <classes> is supported if so. Did you try this?
<includes>${build.testOutputDirectory}/org/permacode/atomic/domain/entity/*.class</includes>
Just checking before I diagnose for you,
Yes, I mean 1.1-SNAPSHOT actually.
Is this not the correct documentation?
http://mojo.codehaus.org/openjpa-maven-plugin/enhance-mojo.html
