Eclipse Community Forums: Eclipse Platform » Prevent plugin installation or warn users about JVM versions

Help

Home

Home » Eclipse Projects » Eclipse Platform » Prevent plugin installation or warn users about JVM versions

Show: Today's Messages :: Show Polls :: Message Navigator

Prevent plugin installation or warn users about JVM versions [message #328932]

Fri, 06 June 2008 20:35

John J. Barton

Messages: 311
Registered: July 2009

Senior Member

I was very surprised to learn that the Update manager does not check the
Java Virtual Machine requirements when installing plugins. I'm not sure
what is the point of having the Execution Environments part of the UI in
on the plugin.xml for PDE. The value isn't checked right?

I am wondering if there is any way to warn users who have say JVM 1.42
and install my plugin developed on Java 1.5. I guess I can put it in
the license page, but no one reads that. Any other suggestions?

Thanks,
John.

Report message to a moderator

Re: Prevent plugin installation or warn users about JVM versions [message #329072 is a reply to message #328932]

Thu, 12 June 2008 04:59

Walter Harley

Messages: 847
Registered: July 2009

Senior Member

"John J Barton" <johnjbarton@johnjbarton.com> wrote in message
news:g2c6op$mc0$1@build.eclipse.org...
>I was very surprised to learn that the Update manager does not check the
>Java Virtual Machine requirements when installing plugins. I'm not sure
>what is the point of having the Execution Environments part of the UI in on
>the plugin.xml for PDE. The value isn't checked right?
>
> I am wondering if there is any way to warn users who have say JVM 1.42 and
> install my plugin developed on Java 1.5. I guess I can put it in the
> license page, but no one reads that. Any other suggestions?

Hi, John. There's a related bug with a lengthy discussion at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=174515 - that bug concerns
plugins that don't load because of platform requirements, as opposed to the
update manager issue, but the issues are very similar. You might want to
familiarize yourself with the various arguments in that bug.

Also, as you may or may not be aware, the old Update Manager has basically
been replaced by the new Provisioning work ("p2"). I don't know whether p2
treats this issue differently.

Keep in mind that the JVM someone is running when they run an update may or
may not be the same as the one they then run the app under. My own thought
would be that at update time, the update manager should warn along the lines
of "to run this plugin, you will need to use Java xxx"; the behavior at
runtime is discussed in the above-mentioned bug.

Report message to a moderator

Previous Topic:	Platform.getBundleGroupProviders() fails
Next Topic:	why eclipse load the old plugin

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Nov 14 09:05:27 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter