Skip to Content.
Sympa Menu

perfsonar-dev - Re: [GN2-JRA1] perfsonarUI - which Java version is preferred ? [was: [pS-dev] flow S&A MA GUI as perfsonarUI plugin?]

Subject: perfsonar development work

List archive

Re: [GN2-JRA1] perfsonarUI - which Java version is preferred ? [was: [pS-dev] flow S&A MA GUI as perfsonarUI plugin?]


Chronological Thread 
  • From: Uros( Juvan <>
  • To:
  • Cc: GN-JRA1-list <>,
  • Subject: Re: [GN2-JRA1] perfsonarUI - which Java version is preferred ? [was: [pS-dev] flow S&A MA GUI as perfsonarUI plugin?]
  • Date: Tue, 05 Jun 2007 14:03:19 +0200
  • Organization: ARNES

It is simple. Class version number is newer when produced by Java 6. As
you already know, there is no problem with Java 6 running classes
produced by Java 5.

However there are problems when classes produced by Java 6 are ran in
Java 5 environment.

Unless of course if you add very important flag to either javac command
line compiler or ant javac target:

1. javac command line option example:
$ javac -target 1.5 SomeClass.java

2. ant javac target:
...
<javac srcdir="someDir" destdir="someDir" target="1.5">
<classpath refid="someId" />
</javac>
...

You should be able to run resulted class using either Java 5 or Java 6 RE.

Tsompanidis Ilias wrote:
> Hello Rolland, all,
> we have had some problems while the developers were using java 6 to
> compile everything, and with users using java 5.
> Everything worked OK when the developers used java 5. (and worked OK on
> machines with java 6)
> So in means of backwards compatibility (and cross platform compatibility
> - for example there is no official update to java 6 for macs), I would
> propose sticking with java 5, unless necessary ;)
>
> Greets,
> Ilias
>
> Roland Karch wrote:
>> At 09:37 05.06.2007, Nina Jeliazkova wrote:
>>> I think the best is to get user and developers feedback on this issue.
>>>
>>> Currently perfsonarUI compiles under Java 5.0 and higher. Gijs
>>> submitted some
>>> plugin UI code which needs Java 6.0. So far the options for
>>> perfsonarUI are:
>>>
>>> - Upgrade to Java 6.0 and abandon 5.0 support;
>>> - Stay with Java 5.0 for now and provide different build file for the
>>> plugins;
>>> - Force all plugins to use same version (Java 5.0 currently);
>>> - Anything else?
>>
>> For the BWCTL plugin, my Java development environment is currently
>> version 5. I really have no idea about the implications of upgrading
>> to 6. I'd assume it just requires a download from SUN and then to
>> recompile everything. If so, it would be nothing more than a minor
>> inconvenience since Java 5 is already bundled with Debian, and I'd
>> have to maintain an installation on my own if I were to upgrade.
>>
>> A different build file for plugins might be a good idea though, I
>> really don't like my current hack of just adding the build
>> instructions to the main PerfsonarUI build file.
>>
>> Greetings,
>> Roland
>>
>> --
>>
>> Roland Karch
>> DFN-Labor
>>
>> Friedrich-Alexander-Universität Erlangen-Nürnberg
>> Regionales RechenZentrum Erlangen (RRZE)
>> Martensstrasse 1
>> 91058 Erlangen
>> Germany
>>
>> Tel.: +49 9131 85-27806, -28800
>> Fax: +49 9131 302941
>>
>>
>> <mailto:>
>> www.rrze.uni-erlangen.de
>> <http://www.rrze.uni-erlangen.de/> www-win.rrze.uni-erlangen.de
>> <http://www-win.rrze.uni-erlangen.de/>
>>

Regards,
--
Uros Juvan
ARNES



Archive powered by MHonArc 2.6.16.

Top of Page