Yes, that's the case. The current Jenkins version used at the ASF can
no longer use JDK5, unless we start using toolchains :-)

We stumbled across that for the Apache Rat builds as well, and changed
to JDK6 to make the builds pass. Using a conbination of animal-sniffer
and maven-enforcer makes a best effort to catch any JDK6 API usage
from leaking into our builds.

On Fri, Nov 14, 2014 at 3:59 AM, Kristian Rosenvold
<[email protected]> wrote:
> Yeah. But in this case the project itself builds fine with JDK1.5, and
> the problem appears to be within jenkins itself. Or maybe jenkins
> stopped supporting 1.5 like we should do too :)
>
> Kristian
>
>
> 2014-11-13 22:02 GMT+01:00 Greg Trasuk <[email protected]>:
>>
>> That error usually means that you’re running under an older JVM.  One of the 
>> jar files has a class version number that is higher than the running JVM 
>> knows about.  e.g. compiled under JDK8, running under JDK6 or something like 
>> that.
>>
>> If you have access to the Jenkins build configuration, have a look and see 
>> if there’s an option for what JVM to use for the build.
>>
>> Cheers,
>>
>> Greg Trasuk
>>
>> On Nov 13, 2014, at 3:45 PM, Kristian Rosenvold 
>> <[email protected]> wrote:
>>
>>> Life with jenkins is interesting as always; this one is new to me
>>> https://builds.apache.org/job/maven-shared/
>>>
>>> Kristian
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to