Summary: | Prechecking during install is needed | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Greg Adams <greg_adams> |
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dejan Glozic <dejan> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P1 | ||
Version: | 2.0 | ||
Target Milestone: | 2.1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Greg Adams
2002-07-08 12:09:02 EDT
The workaround for V5 will be for us to fully drop te entire product irrespective of whether or not we are installing on top of an existing product. Thus we are technically not blocked and so I have oly tagged this as major. I believe this only happens when require is used, no ? In this case how can we user will install feature 1 that requires plugin 1 v 1.0.0, (the plugin is not included, it is required) 1) user has plugin 1 v 1.0.1 installed. We prompt the user saying it may not run, or shouldn't we and we should a) attempt to install 1.0.0 anyway b) not say anything and pretend it will work fine at runtime (higher version) 2) same but with lower version 3) the plugin does not exist. Should we force the user to search for it ? prevent the install like in linux ? IMHO I would prevent install on #2 and #3 and do not say anything for #1 considering it should be backward compatible Thoughts ? We will not address this particular defect for 2.0.2, however we will touch 'requires' support in features and enhance it so that: 1) 'match' is supported (didn't work in 2.0.2) 2) requires on a feature (instead of a plug-in) can be specified. We beleive that the above two enhancements will address the problem. The above sentence under 1) should read 'didn't work in 2.0.0/2.0.1' Addressed in 2.0.2 - code rolled into 2.1. |