enforcer:enforce and not forking lifecycle for surefire and cobertura?

[Barrie Treloar <ba...@gmail.com>]

I've got enforcer up and running, but now I am pushing releases (via
Jenkins) I have noticed in the build output :

INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[INFO] Forking My Project X.Y.X-SNAPSHOT
[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[INFO]
[INFO] --- maven-enforcer-plugin:1.1.1:enforce
(enforce-plugin-versions) @ my-module ---
[INFO]

Once for each module, and lots of times during the release process...
the plugins seem to be the culprits:
--- maven-surefire-plugin:2.12:test
--- cobertura-maven-plugin:2.5.1:instrument

I've not really thought about it much, and it probably isn't doing
much damage (except to my sensibilities) but is it possible to not
have to fork?

Looking at http://maven.apache.org/developers/mojo-api-specification.html
I can't work out why its forking at all.
This is not an area I am familiar with.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org