I now see in build.xml where 1.5 is specified several times. I assume
Jenkins is using that to build?
What threw me was everything still worked for me after I added the new
1.6-only jmdns.jar. The issue seems that I had Eclipse set to 1.5
"compliance", but I was still using the 1.6 JDK, so no errors. Even after I
pointed to the 1.5 JDK, I can run the Ant Build fine, but I now get a
runtime error: "java.lang.UnsupportedClassVersionError: Bad version number
in .class file", when trying to use the ZeroConf stuff.
It also looks like ExternalLinkContentViewerUI.jar is compiled for 1.6, but
JMRI appears to keep running, only outputting "ContentViewerClass
jmri.util.ExternalLinkContentViewerUI doesn't exist". I don't know what
that is, so I don't know if that's a problem or not.
Learning every day,
On Wed, Jul 27, 2011 at 11:43 AM, david d zuhn <zoo@...:
> > Anyone, what is the correct JDK/JRE level? I guess the question is what
> > level is the Jenkins jar builder set to? I'd like to update the
> > to the latest, but it requires 1.6, and that did not work a while back.
> > someone can tell me where to see that setting in Jenkins, that would be
> > great.)
> As a project, JMRI is still on a Java 1.5 compatibility level. It
> just so happens that the JVM on the Jenkins server is 1.5 only.
> A switch to 1.6 (hey, it's only been out for 5 years now) will add all
> sorts of potentially useful things. But it will also halt our
> support on many older machines, for which a 1.6 JVM is not available.
> I believe that includes all PPC Mac OS X machines, Windows 98,
> Windows ME, and Mac OS X 10.4 and earlier (even on Intel CPUs).
> Given how many JMRI users are trying to use older computers for the
> railroad, a switch to 1.6 will annoy some people.
> On the other hand, it is fairly inexpensively for someone to get their
> hands on a used computer that's still new enough to run something with
> a supported OS & JVM, as compared to the rest of the costs for a JMRI
> configuration (one local guy spent more on the LocoBuffer-USB than on
> his computer). Especially since Linux can be gotten for free, and
> works well on new or older computer systems.
> There's been some talk recently of switching to 1.6 compatibility
> (especially with 1.7 just about to come out), perhaps after the next
> major release of JMRI.
> I think that the benefits we gain from switching to 1.6, and
> aggressively using some of the good UI support (like using a real web
> browser for help instead of the mini-browser) are worth it. But we'll
> have to warn the community of the impending change, so those with
> older unsupported systems have some fair chance to deal with the
> david d zuhn Saint Paul Bridge & Terminal Ry.
> zoo @ stpaulterminal.org
> Got Input? Slashdot Needs You.
> Take our quick survey online. Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> Jmri-developers mailing list