Cobertura, profiles and surefire plugin

[Ian Young]

There's a known peculiarity of the current version of Cobertura that requires the Maven Surefire plugin to be configured with this:

	<argLine>-XX:-UseSplitVerifier</argLine>

If you don't do this, you get messages about "expecting a stackmap frame at branch target" when the site goal is used, and zero coverage reported.

In our current V3 parent POM, this configuration is applied in both of the named profiles (release and endorsed), but not in the default state. The result is site generation only works if you apply a named profile; this may actually be the reason behind something I've been wondering about for a while, which is the observation that *every one* of our Jenkins jobs uses the "release" profile.

Question: can anyone think of a reason why the default state of the surefire plugin should not be to use the split verifier, so that Cobertura will work?

If we can't think of a reason, I propose that I try moving the configuration around to have that effect some time next week. This will slightly simplify the release profile, too, which has to be a good thing: I can't believe that releases (vs. normal work) require *quite* so many configuration differences, and it may be we've ended up with stuff there that has nothing to do with releasing.

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5943 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20140130/5f3c5848/attachment.bin