Hi,

If you actually released Cobertura itself using Java7 without special
configuration, then yes.
The bytecode is not gonna be loadable by any jvm lower than the 7 version.

Btw, I just checked the bytecode of some class (PackageCoverage) of the jar
that can be found in central, the class is actually having 0x33 => 51 value
as major version (which is JDK7).

Btw, if you're targetting java5, I'd advice you to use a JDK5 to help
prevent any issue (those can be detected through some additional maven
plugins, but I think it's better to see those as security more than
something else if you don't depend on some upper jdk specificity).

-- Baptiste


2013/6/26 Steven Christou <schristo...@gmail.com>

>  I am having some trouble getting the cobertura plugin to work in bamboo.
> I released a new version of cobertura (version 2.0.1) which fixes a few
> bugs for the maven plugin. I get the exception class file has wrong
> version 51.0, should be 49.0 which leads me to believe it could be an
> issue with cobertura itself. I compiled and ran cobertura using java 7
> (class version 51) however I believe the class version 49 is java 5. Does
> this mean I should re-release cobertura with a --source and --target of 1.5?
>
> Thanks,
> Steve.
>



-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Reply via email to