Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set.
Issue Links
- is related to
-
MJAR-30
Allow includes/excludes specification
-
-
SUREFIRE-180
Ability to add additions to classpath
-
- relates to
-
MNG-1330
direct support for mock classes
-
I think there is an open issue to do this WRT mock classes and maybe actually creating a mock source directory.
Other than that, I think adding features like this is a slippery slope. A lot of Maven's features work and are simple because of the 1 source directory, 1 artifact rule. Anything that starts to product multiple artifacts with a subset of a source directory might not integrate well with other features.