| Summary: | Cannot update Eclipse Platform in JEE package | ||
|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Tobias Oberlies <t-oberlies> |
| Component: | jee-package | Assignee: | Project Inbox <epp.packager-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, kaloyan |
| Version: | 1.4.0 | ||
| Target Milestone: | 1.4.0 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
It is intentional. Though, I'll admit, questionable. In the 'dup' bug 345503 this issue was discussed, and there is some desire to "lock down" exactly what is installed for our packages (for predictable and consistent behavior) but also a desire to be able to update easily. Unfortunately the current situation is some things can be easily updated, but some things not, so this "compromise" does not really satisfy anyone. (or, either use case, I should say). I'd be reluctant to change in Indigo maintenance, since might introduce unexpected behavior ... but, I agree the current situation is not very helpful, such as to update to 4.x. Is updating to 4.x your use case ... or, something else? My preference would be to "lock down" ever feature ... but, then have some easy ways to update to different levels of platform, etc. That way, it is easier for providers to control what they are ready to "release to the world", but at same time, a little more under users control since they can have some choices. In energy you can put into a solution would be great. Thanks. *** This bug has been marked as a duplicate of bug 345503 *** |
The Indigo JEE package doesn't allow to update the Eclipse Platform feature ('org.eclipse.platform.feature.group'). Is this intended or is this a bug? Steps to reproduce: 1. Download the Indigo JEE package (MD5: 321f3fe0ab0c70e3af89173e9ae35816 eclipse-jee-indigo-win32-x86_64.zip) 2. Try to install the Eclipse Platform feature from the software site http://download.eclipse.org/eclipse/updates/3.7.x/M20110728-1200/ The following requirement in the Java EE IDE Feature (id='org.eclipse.epp.package.jee.feature.feature.group' version='1.4.0.20110615-0550') seems to be the root cause: <required namespace='org.eclipse.equinox.p2.iu' name='org.eclipse.platform.feature.group' range='[3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f,3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f]'/>