[
https://issues.apache.org/jira/browse/OPENJPA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718088#action_12718088
]
Michael Dick commented on OPENJPA-1130:
---------------------------------------
The enhancer has never handled jarred classes very well.
If we rely on the enhancer my guess would be that doing a top down build would
work (maven operates on target/test-classes in this case), but building just
the module will fail (maven picks up the jar from .m2/repository). I'd expect
the same behavior for test-jar or a separate module though.
Maybe I need to read more on the validation aspect of JPA 2.0. Are we relying
on the entities having been enhanced, or do we need to re-enhance them? If it's
the former we can probably reorder the enhancement to occur before test-jar
does its work. For the latter we'll have to unjar or improve the enhancer to
handle jarred classes.
> Create a openjpa-testsupport module to share base TestCase classes across
> modules
> ---------------------------------------------------------------------------------
>
> Key: OPENJPA-1130
> URL: https://issues.apache.org/jira/browse/OPENJPA-1130
> Project: OpenJPA
> Issue Type: Test
> Components: build / infrastructure
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1130-tests-classifier.patch.txt,
> OPENJPA-1130.patch
>
>
> Propose moving
> openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/persistence/test/*
> base testcase classes to a openjpa-testsupport JAR which can be shared
> between o-p-j, openjpa-slice and new ones being added to openjpa-integration
> for bean validation and eventually OSGi.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
