| User experience when JRE does not meet Plugin Bundle-RequiredExecutionEnvironment [message #303855] |
Wed, 24 May 2006 14:55  |
Eclipse User |
|
|
|
Originally posted by: dave_pace.hotmail.com
I have a feature whose plugins require JRE 1.5. It appears I can set
this requirement, but it must be at the Plugin with
Bundle-RequiredExecutionEnvironment rather than at the Feature level. I
would prefer if the feature could not be installed rather than failing
at startup but the most important thing is that the user be notified of
the problem.
I've set Bundle-RequiredExecutionEvironment: J2SE-1.5 in one of the
feature's plugin's MANIFEST.MF. I then attempt to install the feature
from an updatesite using Eclipse3.2RC1 with -vm set to JRE 1.4.2
The problem is that when the user installs the feature and restarts the
workbench, the perspectives, views, etc. are hidden from the user but
the user is not notified why. The user can go into Help -> Software
Updates -> Manage Configuration and see the feature is listed there in
good status. However, the feature and plugins are unavailable and not
listed in Feature or Plugin Details from the About page.
Is this the expected behavior? Is there something more I can do to give
the user more information in this case?
Thank you in advance,
Dave
|
|
|
| Re: User experience when JRE does not meet Plugin Bundle-RequiredExecutionEnvironment [message #304109 is a reply to message #303855] |
Tue, 30 May 2006 19:49  |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Dave Pace" <dave_pace@hotmail.com> wrote in message
news:e52a7p$aq4$1@utils.eclipse.org...
> The problem is that when the user installs the feature and restarts the
> workbench, the perspectives, views, etc. are hidden from the user but the
> user is not notified why.
We have the same problem with some of our 1.5-dependent plugins. The
1.4-based user is "notified" in the sense that the platform adds a message
to the error log, saying something about the feature not being loadable due
to required environment. But since unsophisticated users don't in general
know to look at the error log, that's not much help.
You could have another plug-in that is able to run on 1.4 and that is able
to determine whether your main plug-in got successfully loaded (e.g., it
could expose an extension point that your plug-in extends; at runtime, if it
saw no extensions it could complain in some way). But that does seem like
an awful lot of overhead for something that does nothing in the normal case.
|
|
|
Powered by
FUDForum. Page generated in 0.05281 seconds
Home