[
http://jira.codehaus.org/browse/MOPENJPA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202527#action_202527
]
Mark Struberg commented on MOPENJPA-17:
---------------------------------------
I'm aware of this behaviour with 1.0.
But did you test this with the latest snapshots test-enhance mojo?
This should do exactly what you need! Please report back if this worked for you
> Dependencies with scope test must be on enhancement classpath as well
> ---------------------------------------------------------------------
>
> Key: MOPENJPA-17
> URL: http://jira.codehaus.org/browse/MOPENJPA-17
> Project: Maven 2.x OpenJPA Plugin
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Michael Vorburger
> Priority: Minor
>
> There is a small problem if you have a say project A which has a dependency
> to a Project B with <classifier>tests</classifier> & <scope>test</scope> à la
> http://maven.apache.org/guides/mini/guide-attached-tests.html and code in A's
> src/test/java (even if not Entities to be enhanced, say some JUnit) which
> references classes in B's src/test/java (say some JUnit
> helpers/infrastructure).
> The [openjpa:enhance {execution: enhancer}] will fail with a
> java.lang.IllegalArgumentException: java.lang.NoClassDefFoundError: [some
> class in B's src/test/java] at serp.util.Strings.toClass(Strings.java:164)
> although I would argue it should not - from a Maven set-up perspective, the
> project is valid (and compiles fine and all).
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
