Community
Participate
Working Groups
Install latest release runtime can fail in case latest stable runtime is already installed. The problem occures because I'm using the IMetadataRepositoryManager to find the latest version of "org.eclipse.rap.runtime.sdk.feature.group". When the latest stable runtime is already installed the IMetadataRepositoryManager caches its p2 repositories. During the search for the latest release version the repositories for latest stable build are also contacted. Therefore, a wrong version is found because usually the latest stable build runtime has a newer version of "org.eclipse.rap.runtime.sdk.feature.group". This cases the runtime installation to fail with the error message "org.eclipse.rap.runtime.sdk.feature.group not found".
Created attachment 196197 [details] fixes the search for "org.eclipse.rap.runtime.sdk.feature.group" This patch fixes the way the latest version of "org.eclipse.rap.runtime.sdk.feature.group" is searched. IMetadataRepositoryManager is no more used. Only the selected p2-repository (latest build or latest release) is searched now. I used IMetadataRepositoryManager because I thought we will have more then one repository for latest release or latest build in the future. Now we created the composite repositories bug 346521 and this no more the case.
Holger, can you please review this patch? Since downloading the runtime from the RAP repositories is a new feature in this release, I think we should include this fix in the next RC - just by its description, I didn't review the code yet.
I reviewed the patch and I think we are good to go for it. I added some //$NON-NLS-1$ tags. I also tested the bug and the fix. It's also good that you created the tests Beyhan ;). I committed the changes to CVS HEAD and the 1.4 maintenance branch.