Community
Participate
Working Groups
In an IDE that doesn't have a 6.0 JRE available, create an plug-in project with a JavaSE-1.6 Execution Environment using the wizard. The project will have an error, but there is no error mark in the MANIFEST.MF itself so the user is left a little confused what needs to be changed to fix the problem. Open the MANIFEST.MF to remove the Execution Environment dependency on JavaSE-1.6 and save the file. The error in the project remains. Apparently one needs to invoke Update Classpath, but it seems to me that step shouldn't be necessary since I clearly changed something that requires the classpath to be updated. So I think there are two problems. One is that the MANIFEST.MF should have an error marker for its unsatisfied execution environment dependency and changing that dependency should fix the problem without additional steps.
Hrmmm, I guess this enhancement wasn't "Ed proof" :/ The solution here will be to not allow users to select an EE if there are no compatible installed JRE matches. The update classpath action is invoked when you create a new project with the proper EE selection. What was going on is we were trying to update the classpath when there were no compatible installed JREs.
Created attachment 85876 [details] org.eclipse.pde.ui.patch Adds more validation to the new plug-in project wizard. If a user selects an EE that doesn't have any compatible installed JRE matches, a proper error message will be displayed so people like Ed don't select bad EEs.
Created attachment 85877 [details] mylyn/context/zip
Looks good to me Chris. Figured I would take a peak since the patch was not too long.
Fixed in Ed's honor.
Verified on I20080204-0010
