[ 
https://issues.apache.org/jira/browse/OPENJPA-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18143673#comment-18143673
 ] 

ASF subversion and git services commented on OPENJPA-3077:
----------------------------------------------------------

Commit 9d93cfd452bc33899989f5db5b8286a9c477e4bc in openjpa's branch 
refs/heads/OPENJPA-3077 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=9d93cfd45 ]

[OPENJPA-3077] Run the test-dynamic-enhancer profile without security manager 
and installed kernel jar

The root profile enabled the security manager, which the forked test JVM
rejects on JDK 24+ and which kills the surefire fork on JDK 17/21 with the
old policy file. Being a profile of the root POM it also deactivated the
default test-derby profile. Remove it together with the leftover policy.file
profiles, and attach the agent through a manifest-only jar built in
openjpa-persistence-jdbc so the reactor's kernel classes are used.

The profile also removes target/test-classes before compiling, because test
classes left over from a normal build are already enhanced and are not
compiled again.


> test-dynamic-enhancer is broken
> -------------------------------
>
>                 Key: OPENJPA-3077
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-3077
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: instrumentation, jdbc, kernel
>    Affects Versions: 4.1.1
>            Reporter: Maxim Solodovnik
>            Assignee: Maxim Solodovnik
>            Priority: Major
>             Fix For: 4.2.0
>
>
> No tests are successful if {{test-dynamic-enhancer}} profile being used



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to