-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define argLine property rather than setting it in surefire, to ease integration with other plugins #298
Comments
I am not clear about this one. Can be added at maven top level in the pom? i.e. applies to the JVM that runs maven or to a forked JVM? Or you mean surefire.argLine? Re spring-loaded, we tried a lot but since tomcat is not forked we were not able to pass parameters via Maven but we had to call maven with the agent. C Can you elaborate a bit on this issue? Moving to enhancement and post 2.1.1. |
I mean that the argLine parameter should be defined as a property of the pom, rather than a configuration of surefire.
This has the same effect, but allows other plugins - such as JaCoCo - to alter this value. |
Allows other plugins (such as JaCoCo) to tune the argLine parameters of the JVM forked by surefire
…re, to ease integration with other plugins, #298
#298 Define argLine as a property, not in surefire
The parent pom of the SDK currently defines this:
This makes it impossible for other plugins to redefine this argLine setting.
My use case is the maven-jacoco-plugin, which adds a java agent on the command line to generate some code coverage.
The warning at the beginning of that page explains it very well.
It would be much more convenient not to configure this in the surefire plugin, but just defining the
argLine
property:(And by the way, this could be a nicer way to add the spring-loaded argument on the command line too...)
The text was updated successfully, but these errors were encountered: