| Re: JRE 1.4.2 with Eclipse 3.4? [message #578096] |
Mon, 29 September 2008 16:22 |
 Eric Rizzo
Messages: 3070
Registered: July 2009 |
Senior Member |
|
|
On 9/27/2008 3:39 PM, Walter Harley wrote:
> "Ed Merks"<Ed.Merks@gmail.com> wrote in message
> news:gbjb97$c93$1@build.eclipse.org...
>> Peter,
>>
>> That's a very good point. It looks to me like Eclipse Classic is the only
>> download that doesn't require Java 5.0. That makes the recommendation at
>> the top of the page awfully weak. Please open a bugzilla asking to make
>> the statement more strongly. In fact, there really ought to be a way to
>> find out the JRE level required for any particular package, and currently
>> it's guesswork; that's no good. The other things ought to be fixed up as
>> well. When you open a bugzilla, please append the bugzilla number to this
>> thread.
>
> The issue is really kind of trickier than it seems on the surface. See
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=174515 for a related topic.
>
> I do think that clearer documentation on the web site would help, and I
> think we should simply be recommending that people use the newest JVM
> version they can, and understand that if they're on a downlevel VM some
> functionality may be missing. The way I would put it is: "Most of the
> Eclipse core is able to run on Java 1.4.2, but every version of Eclipse
> contains some functionality that relies on Java 5 or even Java 6. You may
> not need this functionality, depending on what you're doing with Eclipse."
>
> The problem is that describing exactly what functionality is and is not
> available on a given VM quickly gets into way more detail than is
> appropriate for a downloads page. Someone planning on using Eclipse to edit
> PHP scripts shouldn't have to read about the JSR199 API, for instance.
>
> I really think it comes down to the question of how we show that some
> functionality is unavailable, without intruding on the experience of people
> who don't need that functionality. Unfortunately, that is a very hard
> challenge.
I actually think the problem in Peter's particular case is that the
"Eclipse IDE for Java Developers" package specifies
"-Dosgi.requiredJavaVersion=1.5" in its eclipse.ini
While I understand that Mylyn requires 1.5, I don't think anything else
that is "crucial" to the Java dev tools does, so it seems to me that
this is an unnnecessary restriction for that package (Mylyn is, IMO,
still an optional piece of functionality that should not prevent the
entire tool from loading).
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=248976 about this.
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.02599 seconds
] 
Search
Help
Register
Login
Home
