| jdk 1.5, and early release stuff [message #49222] |
Wed, 04 June 2003 18:12  |
Eclipse User |
|
|
|
Originally posted by: tgm1024SiteNameMispelled.hotmale.com
If I were to install the sun early adopter stuff for experimenting with
generics and other things, will eclipse work ok with it even though the
eclipse syntax engine itself will not like things like
List<String> list = new ArrayList<String>();
?
Thanks.
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: jdk 1.5, and early release stuff [message #52649 is a reply to message #52622] |
Sat, 07 June 2003 18:09  |
| Eclipse User |
|
|
|
Originally posted by: tgm1024SiteNameMispelled.hotmale.com
In news:bbtko3$2f2$1@rogue.oti.com,
Johan Compagner <jcompagner@j-com.nl> spoke unto us:
>>>> Why doesn't eclipse have a simple option:
>>>>
>>>> O turn off jdk specifics
>>>
>>> What would that do?
>>
>> Turn off anything within eclipse that was specific to a particular
>> jdk release.
>
> Such as?
>
>
> What is specific to a particular JDK?
Numerous language changes in 1.5. Generics, for loop iterator enhancement,
Boxing/unboxing of primitives, yadda. These require a different javac.exe
and eclipse is bound to it's internal compiler's revs.
There should be a way to turn off the jdk revision specific stuff, hence
turn off its reliance upon the internal compiler, to just allow external
compilation. Visual Cafe for Java used to do just that, back when it was
alive before borland bought 'em. You had a crap load of fields to fill out,
but you could set it up to use any jdk release when they ended up obsoleting
the one built into the ide.
But you answer yourself in the following paragraphs.
>
>
>>>> or
>>>>
>>>> O Allow experimental jdk's such as early adoptions
>>>
>>> ...and what would that do? You can use "experimental JDKs"
>>> fine as it is.
>>
>> You seem to be at odds with everyone else's post in this thread.
>
>
> using a JDK (the jre of the jdk) can be used perfectly fine
> (If you had the JDK1.5 beta now you could use it for running and
> debugging)
Sure, if that's all you want it for. I tend to use an IDE for /compiling/
too.
> The problem with JDK1.5 that javac is changed pretty much and the
> internal compiler of eclipse has to catchup.
>
> johan
RIGHT. Which according to folks here, means that I cannot develop using
1.5-isms with eclipse as it stands before rev 3.0.
|
|
|
| Re: jdk 1.5, and early release stuff [message #53196 is a reply to message #52649] |
Mon, 09 June 2003 09:07 |
| Eclipse User |
|
|
|
> Numerous language changes in 1.5. Generics, for loop iterator enhancement,
> Boxing/unboxing of primitives, yadda. These require a different javac.exe
> and eclipse is bound to it's internal compiler's revs.
>
> There should be a way to turn off the jdk revision specific stuff, hence
> turn off its reliance upon the internal compiler, to just allow external
> compilation. Visual Cafe for Java used to do just that, back when it was
> alive before borland bought 'em. You had a crap load of fields to fill out,
> but you could set it up to use any jdk release when they ended up obsoleting
> the one built into the ide.
Just turn off auto build and make a ANT builder that uses the javac command.
Of course the Java Editor will still not understand generics code
and i think there will be other problems that could also arise for
example with code completion..
>
> Sure, if that's all you want it for. I tend to use an IDE for /compiling/
> too.
with an ant builder this should be possible,
>
> > The problem with JDK1.5 that javac is changed pretty much and the
> > internal compiler of eclipse has to catchup.
> >
> > johan
>
>
> RIGHT. Which according to folks here, means that I cannot develop using
> 1.5-isms with eclipse as it stands before rev 3.0.
1.5 isn't even out yet (and i mean out as the first beta)
of course you could use the early adaptor generices lib for looking at it.
But i wouldn't build any code with it as long as the first beta's or RC are
appearing. Because it is still a running target. That's why i believe
eclipse won't support it in the first Milestones of the 3.0 release.
Because then they are constantly playing catchup. Hopefully the generices
spec will stablelize as soon as possible.
But even if an ide had just a javac call. Then i still believe that the IDE
has to be alterd to support all the new syntax (think about the editor)
I also don't know exactly which roadmaps ends first the one of eclispe 3.0
or the one of 1.5? If i have to guess then i think we have Eclipse 3.0 final
long before a 1.5 final so if eclise supports it then it is fine by me.
johan
|
|
|
| Re: jdk 1.5, and early release stuff [message #53274 is a reply to message #52649] |
Mon, 09 June 2003 11:21 |
| Eclipse User |
|
|
|
"Muad'Dib" <tgm1024SiteNameMispelled@hotmale.com> wrote in message
news:bbtnuc$3l1$1@rogue.oti.com...
> Johan Compagner <jcompagner@j-com.nl> spoke unto us:
> >>>> Why doesn't eclipse have a simple option:
> >>>>
> >>>> O turn off jdk specifics
> >>>
> >>> What would that do?
> >>
> >> Turn off anything within eclipse that was specific to a particular
> >> jdk release.
> >
> > Such as?
> >
> > What is specific to a particular JDK?
>
> Numerous language changes in 1.5. Generics, for loop iterator
enhancement,
> Boxing/unboxing of primitives, yadda.
A "turn off jdk specifics" option would help with this not in the slightest.
> There should be a way to turn off the jdk revision specific stuff, hence
> turn off its reliance upon the internal compiler, to just allow external
> compilation.
There already is - use javac, jikes - or whatever - as an external tool.
See the "Run > External tools" menu.
> Visual Cafe for Java used to do just that, back when it was
> alive before borland bought 'em. You had a crap load of fields
> to fill out, but you could set it up to use any jdk release when
> they ended up obsoleting the one built into the ide.
So - do that with Eclipse - if you really want.
It can call command-line utilities like the best of them.
--
__________
|im |yler http://timtyler.org/ tim@tt1.org
|
|
|
|
| Re: jdk 1.5, and early release stuff [message #66342 is a reply to message #53412] |
Tue, 24 June 2003 14:32 |
| Eclipse User |
|
|
|
Muad'Dib wrote:
>
> Not really---there could be an option like I suggested to turn off anything
> in the editor (and anything else in the ide) that is language specific.
To be honest - if you will turn off java support in eclipse, you end up
with quite big and not very good text editor. There is a plenty of
better tools out there for that. For me, strength of eclipse lies in
tight integration with content you are editing - all metadata about
source code available for entire IDE. Without it, eclipse editor itself
isn't worth enough. You can do a lot better with jedit.
Artur
|
|
|
Powered by
FUDForum. Page generated in 0.65117 seconds
Home