[SUREFIRE-2097] More configuration for surefire JPMS

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-M7
• Assignee: Olivier Lamy
• Reporter: Olivier Lamy
• Created: 09/Jun/22 06:37
• Updated: 28/Jul/23 10:10

Description

Currently surefire manages the build of module path and classpath graph with almost not configurable option.
Due to long time between M5 and M6 releases while in the meantime plexus-java has incorporated a lot changes (for compiler, javadoc), those release has created some backward incompatible changes which are affecting some users such:

• https://issues.apache.org/jira/browse/SUREFIRE-2057
• comments here https://github.com/eclipse/jetty.project/pull/8129

So we need few more options to be able to configure some of the assumptions which has been made and changed in plexus-java.
Because the current configuration is hardcoded:

            ResolvePathsRequest<String> req = ResolvePathsRequest.ofStrings( testClasspath.getClassPath() )
                    .setIncludeAllProviders( true )
                    .setJdkHome( javaHome )
                    .setIncludeStatic( true )
                    .setModuleDescriptor( javaModuleDescriptor );

We must give users some options to override the black magic made by plexus-java.

Options to configure:

• force all test/provided scope to be in classpath or not
• do not add automatically providers to the module path
• a possible list per groupId/artifactId to force module path or classpath
• etc...

The idea here is too collect what users need.
Remember we will try to avoid too much complicated options

Issue Links

• is related to: MNG-7855 Dependencies wrongly put on class-path rather than module-path