Description of the problem or enhancement request:
I succeeded in making a global fakes by setting -Dfakes={fake class package path}
But i wanna know how to set multiple global fakes.
I have tried -Dfakes={fake class package path1}|{fake class package path2} and -Dfakes={fake class package path1}={fake class package path2}, but neither works.
Check the following:
[ ] If a defect or unexpected result, JMockit project members should be able to reproduce it.
For that, include an example test (perhaps accompanied by a Maven/Gradle build script) which
can be executed without changes and reproduces the failure.
[ ] If an enhancement or new feature request, it should be justified by an example test
demonstrating the validity and usefulness of the desired enhancement or new feature.
[ ] The issue does not fall outside the scope of the project (for example, attempting to use
JMockit APIs from Groovy or Scala code, or with an Android runtime).
[ ] The JDK where the problem occurs is a final release, not a development build.
Please provide the following information:
Version of JMockit that was used: 1.49
Description of the problem or enhancement request: I succeeded in making a global fakes by setting -Dfakes={fake class package path} But i wanna know how to set multiple global fakes. I have tried -Dfakes={fake class package path1}|{fake class package path2} and -Dfakes={fake class package path1}={fake class package path2}, but neither works.
Check the following:
[ ] If a defect or unexpected result, JMockit project members should be able to reproduce it. For that, include an example test (perhaps accompanied by a Maven/Gradle build script) which can be executed without changes and reproduces the failure.
[ ] If an enhancement or new feature request, it should be justified by an example test demonstrating the validity and usefulness of the desired enhancement or new feature.
[ ] The issue does not fall outside the scope of the project (for example, attempting to use JMockit APIs from Groovy or Scala code, or with an Android runtime).
[ ] The JDK where the problem occurs is a final release, not a development build.