Java Help - eclipse 3.0 - dose it support jdk1.5.0?

Author

eclipse 3.0 - dose it support jdk1.5.0?

Alex Hunsley

2004-10-12, 8:57 am

I've pointed my eclipse 3.0 to the jdk1.5.0 just fine. But the project
settings for compiler compliance still only allow me to select 1.3 or
1.4 - is there a way around this? Or is compiling jdk1.5.0 code under
eclipse 3.0 a no-no?

alex

Alex Hunsley

2004-10-12, 8:57 am

Alex Hunsley wrote:
> I've pointed my eclipse 3.0 to the jdk1.5.0 just fine. But the project
> settings for compiler compliance still only allow me to select 1.3 or
> 1.4 - is there a way around this? Or is compiling jdk1.5.0 code under
> eclipse 3.0 a no-no?
>
> alex

asked and answered - I've just googled some more, and voila:

http://www.vasanthdharmaraj.com/Per...586c00de11.aspx

ta,
alex

Chas Douglass

2004-10-12, 3:59 pm

Alex Hunsley <lard@tardis.ed.ac.molar.uk> wrote in news:10mnd1u1jhvib34
@corp.supernews.com:

> http://www.vasanthdharmaraj.com/Perma

Also, the 3.1 beta of eclipse has the 1.5 support built in, now, since it
is targeted for that release.

Chas Douglass

Thomas G. Marshall

2004-10-12, 8:57 pm

Chas Douglass coughed up:
> Alex Hunsley <lard@tardis.ed.ac.molar.uk> wrote in
> news:10mnd1u1jhvib34 @corp.supernews.com:
>
>
> Also, the 3.1 beta of eclipse has the 1.5 support built in, now,
> since it is targeted for that release.
>
> Chas Douglass

Download the 3.1M2 build at least.

--
"His name was Robert Paulson. His name was Robert Paulson. His name was
Robert Paulson..."

IchBin

2004-10-13, 9:10 am

Thomas G. Marshall wrote:
> Chas Douglass coughed up:
>
>
>
> Download the 3.1M2 build at least.
>
>
>
My understanding of this support in 3.1 is *misleading*. That is: the
highlighting syntax checker will recognize say the 'enum' but Eclipse
still does not *FULLY* support it. It sorta half ass supports it right
now. Not all of the modules support it. Hope I am wrong but just saw
this discussion in the Eclipse newsgroups. I am on 3.1 and Cheetah will
not support this release, which I guess makes sense, being the target
1.5 support release ..

--

Thanks in Advance...
IchBin
________________________________________
__________________________________

'Laughter is inner jogging'
- Norman Cousins, editor and author (1915-1990)

Alex Hunsley

2004-10-13, 9:10 am

IchBin wrote:
> Thomas G. Marshall wrote:
>
> My understanding of this support in 3.1 is *misleading*. That is: the
> highlighting syntax checker will recognize say the 'enum' but Eclipse
> still does not *FULLY* support it. It sorta half ass supports it right
> now. Not all of the modules support it. Hope I am wrong but just saw
> this discussion in the Eclipse newsgroups. I am on 3.1 and Cheetah will
> not support this release, which I guess makes sense, being the target
> 1.5 support release ..

Thje main concern of mine is that eclipse will compile and run all new
1.5 features ok... syntax colouring etc. I can do without for now. Does
it at least compile and run it ok?

alex

Alex Hunsley

2004-10-13, 9:10 am

Tor Iver Wilhelmsen

2004-10-13, 9:10 am

Alex Hunsley <lard@tardis.ed.ac.molar.uk> writes:

> I assume you maen 3.0.1? I can't find 3.1....

3.0.1 is the latest STABLE release. 3.1 is in "beta". It should be
available starting somewhere from www.eclipse.org.

Thomas G. Marshall

2004-10-13, 4:00 pm

Alex Hunsley coughed up:
> IchBin wrote:
>
> Thje main concern of mine is that eclipse will compile and run all new
> 1.5 features ok... syntax colouring etc. I can do without for now.
> Does it at least compile and run it ok?

Not the complete 1.5. And CMIIW, but netbeans isn't there yet either. It
wasn't even pretending to be 1.5 last I checked.

<crankbot alert/>
See, this is a *huge* failing of eclipse, but the eclipse
robots^H^H^H^H^H^Hpundits seem to see every problem as some whacked sort of
feature. Eclipse really should have allowed an easy entering of an external
compiler, much the way that VisualCafe used to. In Eclipse you can crock
something together using ant, but that seems mighty sketchy to me.

And I jEdit just seems like counter intuitive---I could get it to work, but
it stopped after a while for phantom reasons.

For 1.5 testing, etc., I am using vi for the time being.

>
> alex

--
Iamamanofconstantsorrow,I'veseentroublea
llmydays.Ibidfarewelltoold
Kentucky,TheplacewhereIwasbornandraised.ForsixlongyearsI'vebeenin
trouble,NopleasureshereonearthIfound.ForinthisworldI'mboundtoramble,
Ihavenofriendstohelpmenow.... MaybeyourfriendsthinkI'mjustastrangerMyf
ace,
you'llneverseenomore. ButthereisonepromisethatisgivenI'llmeety
ouonGod's
goldenshore.

Thomas G. Marshall

2004-10-13, 4:00 pm

Alex Hunsley coughed up:

....[rip]...

> I assume you maen 3.0.1? I can't find 3.1....

http://www.eclipse.org/downloads/index.php

And choose 3.1M2. It'll have the latest /stable/ build. And the release
notes will tell you of additional java 5 abilities.

If there are subtle errors here and there, you can often go up to the
{shudder} nightly builds, etc. I've had to do that from time to time with
fairly good results.

But in general, /always/ go with the one just "above" the official release
rev. (listed just under it).

>
> alex

--
Iamamanofconstantsorrow,I'veseentroublea
llmydays.Ibidfarewelltoold
Kentucky,TheplacewhereIwasbornandraised.ForsixlongyearsI'vebeenin
trouble,NopleasureshereonearthIfound.ForinthisworldI'mboundtoramble,
Ihavenofriendstohelpmenow.... MaybeyourfriendsthinkI'mjustastrangerMyf
ace,
you'llneverseenomore. ButthereisonepromisethatisgivenI'llmeety
ouonGod's
goldenshore.

Chas Douglass

2004-10-13, 4:00 pm

IchBin <weconsul@ptd.net> wrote in news:Qqydnc5ysuS6m_DcUSdV9g@ptd.net:

> Thomas G. Marshall wrote:
> My understanding of this support in 3.1 is *misleading*. That is: the
> highlighting syntax checker will recognize say the 'enum' but Eclipse
> still does not *FULLY* support it. It sorta half ass supports it right
> now. Not all of the modules support it. Hope I am wrong but just saw
> this discussion in the Eclipse newsgroups. I am on 3.1 and Cheetah will
> not support this release, which I guess makes sense, being the target
> 1.5 support release ..
>

Sorry, I didn't use enough words. Let me rephrase:

Also, the 3.1 beta of eclipse has THE SAME SUPPORT AS CHEETAH built in,
now, since it is targeted for that release.

In other words, the 3.1 beta (I'm running milestone 2), has the
"cheetah" additions built in.

It is still NOT full 1.5 support, by any means.

Chas Douglass

Chas Douglass

2004-10-13, 4:00 pm

Alex Hunsley <lard@tardis.ed.ac.molar.uk> wrote in
news:10mq7bh692cr09a@corp.supernews.com:

> IchBin wrote:
>
> Thje main concern of mine is that eclipse will compile and run all new
> 1.5 features ok... syntax colouring etc. I can do without for now.
> Does it at least compile and run it ok?
>
> alex

Eclipse is not misleading, although you may have been misled by my
earlier post.

We were specifically discussing "cheetah", the early release support of
1.5 features. That support is available as part of the 3.1 beta of
eclipse, but it is still not complete, by any means.

Chas Douglass

IchBin

2004-10-13, 4:00 pm

Alex Hunsley wrote:
> IchBin wrote:
>
>
>
> I assume you maen 3.0.1? I can't find 3.1....
>
> alex
Yes...... Sorry, the splash screen says 3.1.. really 3.1

Gotta love computer nomenclature..lol

--

Thanks in Advance...
IchBin
________________________________________
__________________________________

'Laughter is inner jogging'
- Norman Cousins, editor and author (1915-1990)

IchBin

2004-10-13, 4:00 pm

Thomas G. Marshall wrote:
> Alex Hunsley coughed up:
>
>
>
> Not the complete 1.5. And CMIIW, but netbeans isn't there yet either. It
> wasn't even pretending to be 1.5 last I checked.
>
> <crankbot alert/>
> See, this is a *huge* failing of eclipse, but the eclipse
> robots^H^H^H^H^H^Hpundits seem to see every problem as some whacked sort of
> feature. Eclipse really should have allowed an easy entering of an external
> compiler, much the way that VisualCafe used to. In Eclipse you can crock
> something together using ant, but that seems mighty sketchy to me.
>
> And I jEdit just seems like counter intuitive---I could get it to work, but
> it stopped after a while for phantom reasons.
>
> For 1.5 testing, etc., I am using vi for the time being.
>
>
>
>
>
>
Try *JGRASP* ...... it supports 1.5

http://www.jgrasp.org/index.html

The jGRASP 1.7.1 release added more support for Java 1.5 features. CSD
generation now fully supports Java 1.5 syntax. The UML diagram shows
enums and generic signatures for classes, fields, and methods. The Java
*debugger and workbench show full generic signatures* with replacements
whenever possible, and allow the user to specify generic type arguments
when creating a class instance. Operations such as "invoke method" still
consider the declared type of values to be the run-time type even when a
replaced type can be resolved - this will be fixed in a future version.

--

Thanks in Advance...
IchBin
________________________________________
__________________________________

'Laughter is inner jogging'
- Norman Cousins, editor and author (1915-1990)

Alex Hunsley

2004-10-14, 4:00 pm

Chas Douglass wrote:
> IchBin <weconsul@ptd.net> wrote in news:Qqydnc5ysuS6m_DcUSdV9g@ptd.net:
>
>
>
>
> Sorry, I didn't use enough words. Let me rephrase:
>
> Also, the 3.1 beta of eclipse has THE SAME SUPPORT AS CHEETAH built in,
> now, since it is targeted for that release.
>
> In other words, the 3.1 beta (I'm running milestone 2), has the
> "cheetah" additions built in.
>
> It is still NOT full 1.5 support, by any means.
>
> Chas Douglass

Chas,
thanks to you and everyone else who replied for the helpful info! :)

alex

Dale King

2004-10-14, 4:00 pm

"Thomas G. Marshall" < tgm2tothe10thpower@replacetextwithnumber
.hotmail.com>
wrote in message news:7Q9bd.1$v_6.0@trndny04...
> <crankbot alert/>
> See, this is a *huge* failing of eclipse, but the eclipse
> robots^H^H^H^H^H^Hpundits seem to see every problem as some whacked sort
of
> feature. Eclipse really should have allowed an easy entering of an
external
> compiler, much the way that VisualCafe used to. In Eclipse you can crock
> something together using ant, but that seems mighty sketchy to me.

No, I wouldn't say that the lag time for language changes is a feature. It
is a tradeoff for the features that having your own compiler gives you. The
cost of getting these great features is that you have the lag time. The lag
time in this case is much greater because the scope and breadth of changes
for 1.5 are so great.

It is certainly a di

vantage to having your own compiler, that changes in
the language require you to change your compiler which can delay support for
those language changes. It is certainly not a *huge* failing, but is an
issue with the decision to have their own compiler.

You are ignoring the advantages they have from having their own more
powerful compiler that enables other features. And I think those advantages
win out big over the slight di

vantage of lag time for new language
changes. Particularly when a few months from now we will have those great
features plus 1.5 support.

Some of those advantages are:

- Improved compiler checks to check for thinks that are not reported by
javac but can be elevated to warnings or errors in Eclipse's compiler or
alternatively you can even turn off some things that are errors in javac.
Here is a list of things you have control over whether they are ignored,
warning, or error:

-- Unreachable code
-- Unresolvable import statements
-- Unused local variables (i.e. never read)
-- Unused parameters (i.e. never read)
-- Unused imports
-- Unused private types, methods or fields
-- Usage of non-externalized strings
-- Usage of deprecated API (also can disable for usage within deprecated
code)
-- Methods overridden but not package visible
-- Methods with a constructor name
-- Conflict of interface method with protected 'Object' method e.g.
interface I { int clone(); }
-- Hidden catch blocks
-- Non-static access to a static member
-- Access to a non-accessible member of an enclosing type
-- Assignment has no effect (e.g. 'x = x')
-- Using a char array in string concatenation
-- Report 'assert' as identifier (use when targetting pre 1.4)

- Better knowledge of dependencies so that you can do incremental
compilation. This allows them to compile on save so you never actually
explicitly have to say compile. This is a *huge* advantage over other IDE's.

- The Eclipse compiler can still generate a class file *even though it has
compiler errors*. Say you have a method that has an error. The compiler will
still generate the method that throws an exception. You can actually debug
code that still has compiler errors. If you never call the method that has
the error your code will run without problems.

- The ability for others to plug into and customize the compilation.

There are probably more that I'm forgetting.

--
Dale King

Thomas G. Marshall

2004-10-14, 4:00 pm

Dale King coughed up:
> "Thomas G. Marshall"
> < tgm2tothe10thpower@replacetextwithnumber
.hotmail.com> wrote in
> message news:7Q9bd.1$v_6.0@trndny04...
>
> No, I wouldn't say that the lag time for language changes is a
> feature. It is a tradeoff for the features that having your own
> compiler gives you. The cost of getting these great features is that
> you have the lag time. The lag time in this case is much greater
> because the scope and breadth of changes for 1.5 are so great.
>
> It is certainly a di

vantage to having your own compiler, that
> changes in the language require you to change your compiler which can
> delay support for those language changes. It is certainly not a
> *huge* failing, but is an issue with the decision to have their own
> compiler.
>
> You are ignoring the advantages they have from having their own more
> powerful compiler that enables other features.

No, I actually understand the notion well. There is /no/ reason that
eclipse couldn't /default/ to having its own compiler, and then allow an
external compiler to be fully specified resulting in a subset of the IDE
features.

....[rip]...

--
Whyowhydidn'tsunmakejavarequireanupperca
selettertostartclassnames....

Sponsored Links