You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2021/03/24 20:35:37 UTC

[GitHub] [maven] mthmulders edited a comment on pull request #456: Run GitHub actions integration tests with Java 16

mthmulders edited a comment on pull request #456:
URL: https://github.com/apache/maven/pull/456#issuecomment-806169235


   I gave BeanShell a try this evening, but I'm greeted with
   
   > Class: javax.enterprise.inject.Instance not found in namespace
   
   So, to summarise:
   
   > @mthmulders that's what the test does yes. The most important is the execution classloader which should rely on the plugin loader, can be done with a .java but must be executed in a mojo classloader (so exec-maven-plugin does a bit too much to test that accurately so not sure about a .java).
   
   If I understand correctly, we can't run this test using the exec-maven-plugin.
   
   From my experience, we can't run it with JUnit and we can't run it with Bsh either. I'm afraid we're running out of options....
   
   I think there are not much other options left than moving to [Groovy 4.0.0-alpha-2](https://github.com/apache/groovy/blob/1136910170fd100fb2d792db95ec08b935f29530/versions.properties#L20) and hoping not every new Java release will see this issue.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org