> Just reverted to 6.0.35
> Looks to be better:
https://builds.apache.org/job/Torque4-trunk/68/console

Thanks a lot! The build looks good now.

> @Torque folks I have changed your cron scm pooling which was * * * * *
> (every minutes) to @hourly
> Please avoid using such value !

Ok, thanks. I looked at the jenkins wiki site

http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson#Are_there_recommended_or_mandatory_Jenkins_settings_for_ASF_projects.3F

and did not find any restrictions there, so I thought every minute was ok.
Perhaps others assume the same so it would be worth documenting a
recommended setting there.

    Thanks,

         Thomas

> 2012/2/16 Olivier Lamy <ol...@apache.org>:
> > The issue is running Jenkins on Tomcat7 with maven build using jdk1.5 .
> > Jenkins jobs (with jdk1.5) try to load some classes (in our cases
> > javax.servlet.* ) from master node.
> > And in this case they come from tomcat classLoader and are "marked"
> > 1.6 result -> "Caused by: java.lang.UnsupportedClassVersionError: Bad
> > version number in .class file"
> >
> > I don't have any quick fix now or workaround. Expect revert Jenkins
> > master running on tc 6.x
> >
> > 2012/2/16 Niklas Gustavsson <nik...@protocol7.com>:
> >> On Thu, Feb 16, 2012 at 9:50 AM, Olivier Lamy <ol...@apache.org>
wrote:
> >>> It's on my TODO list to debug/fix this jenkins issue.
> >>> I will try to work on that today.
> >>
> >> I tried to downgrade the Cobertura publisher mentioned in the
> >> stacktrace to no improvement.
> >>
> >> /niklas
> >
> >
> >
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy

Reply via email to