John- Thanks for all your help in this matter, the environment descriptions do exactly as you say. I ended up removing the JDT setting entirely, so now it uses the workbench default 'warning'. Made for a frustrating afternoon, but truly thanks for your help. Let me know if I may ever be of assistance.
JD ps- in case you were wondering what all that was for: http://bugs.eclipse.org/bugs/show_bug.cgi?id=386277 On Mon, Jul 30, 2012 at 3:25 PM, John Arthorne <[email protected]>wrote: > I think these are unrelated features. The environment descriptions are > part of PDE API tools. They are used by the API tools builder to verify > you are using only API availble in that JRE. See the preferences under > Plugin Development > API Errors/Warnings > API Use > General. What you are > talking about is a JDT setting that will create a compile error if there is > no real JRE matching the execution environment. This will create an error > for you unless you have a real 1.4 JRE install. For what it's worth I have > that set to WARNING rather than ERROR on all my projects, and I expect you > can do the same. > > John > > > > *Joseph D Carroll Jr <[email protected]>* > Sent by: [email protected] > > 07/30/2012 03:46 PM > Please respond to > "Eclipse platform general developers list." < > [email protected]> > > To > [email protected] > cc > Subject > Re: [platform-dev] J2SE 1.4 Execution Environment > > > > > John- > > You are right again, once you install the environment descriptions there > aren't any additional steps (and there are no *.ee files). I am able to > browse to either a project properties page or the workbench properties page > and under Plug-in Development -> API Errors/Warnings it lists the > execution environment descriptions installed. > > However, there still seems to be an issue. The problem comes down to the > preference in .settings -> org.eclipse.jdt.launching.prefs : > > org.eclipse.jdt.launching.PREF_STRICTLY_COMPATIBLE_JRE_NOT_AVAILABLE=error > > If I change 'error' to 'warning' the compile errors go away. If I add a > JDK1.5 the compile errors go away. > > Is this a bug in the > org.eclipse.jdt.launching.PREF_STRICTLY_COMPATIBLE_JRE_NOT_AVAILABLE > preference? > (that it doesn't read the valid environment descriptions) > > Thanks, > > JD > > > On Mon, Jul 30, 2012 at 2:00 PM, John Arthorne > <*[email protected]*<[email protected]>> > wrote: > After installing the descriptions from the repository, I don't think you > need to do anything else (perhaps a rebuild?) I don't even know if there > are corresponding *.ee files that come with those descriptions. > > John > > > *Joseph D Carroll Jr <**[email protected]* <[email protected]> > *>* > > 07/30/2012 02:32 PM > > To > John Arthorne/Ottawa/IBM@IBMCA > cc > Subject > Re: [platform-dev] J2SE 1.4 Execution Environment > > > > > > > John- > > I definitely did not have the environment descriptions installed, didn't > even know they existed. I installed the descriptors for 1.1-1.7 and now I > am trying to add them to the list of installed JRE's but I cannot locate > any of the *.ee files. Any idea on where to look? Once I have the > environment descriptors installed then I will make sure the super interface > errors are still there and file a bug at that point. > > thanks, > > JD > > > > On Mon, Jul 30, 2012 at 1:12 PM, John Arthorne > <*[email protected]*<[email protected]>> > wrote: > Could it be that you don't have all the execution environment descriptions > installed? If you don't have a J2SE 1.4 JRE installed, you need to install > a description file that tells the API tools what the 1.4 JRE looks like. > You can install them from this repository: * > > **http://download.eclipse.org/eclipse/updates/4.3-I-build*<http://download.eclipse.org/eclipse/updates/4.3-I-build> > > I'm not familiar with the "super interfaces set has been reduced" errrors > either. Please enter a bug and we can sort out what's going on there. > > John > > *Joseph D Carroll Jr <**[email protected]* <[email protected]> > *>* > > 07/30/2012 02:05 PM > > To > John Arthorne/Ottawa/IBM@IBMCA > cc > Subject > Re: [platform-dev] J2SE 1.4 Execution Environment > > > > > > > > > John- > > I just determined that the project specific settings were causing my > grief. Specifically the strictly compatible JRE = error setting. I > disabled project specific settings for each of the projects to resolve the > issue. Does that sound reasonable or should I just change the one setting? > (the default seems to be warn) > > Also I get a number of "The super interfaces set has been reduced for type > ..." errors. I'm not too sure I even know what these mean, but is there an > accepted approach to resolving these errors? > For now I created a "commented compatibility problem filter," which > created a .api_filters file. > > Other than these two issues, everything is fixed. I'll create a bug and > send you the id if you want. > > I appreciate the help. Thanks, > > JD > > > > On Mon, Jul 30, 2012 at 11:01 AM, John Arthorne <*[email protected] > * <[email protected]>> wrote: > Typically we don't change the minimum execution environment unless we have > a need for it. However much of the platform has already moved to Java 5 > minimum so I think that would be quite reasonable here. > > John > > *Joseph D Carroll Jr <**[email protected]* <[email protected]>* > >* > Sent by: *[email protected]*<[email protected]> > > 07/30/2012 11:43 AM > > > Please respond to > "Eclipse platform general developers list." <* > [email protected]* <[email protected]>> > > To > *[email protected]* <[email protected]> > cc > Subject > [platform-dev] J2SE 1.4 Execution Environment > > > > > > > > > > > Would anyone happen to know why the platform-debug plugins have an > execution environment of J2SE 1.4? I am beginning work on porting the > Console view to a pure e4 MPart and ran into some compile errors relating > to the J2SE 1.4 requirement. I can work around these issues, however since > I am doing some work here anyways, I wasn't sure if this was something that > should be updated. (say to 1.5 or 1.6) > > Unless I am missing something (which I might be) there are relatively few > code changes necessary to update the execution environment. All of the > changes I found deal with simple casting errors (several of Boolean val = > (Boolean) someString;). IIRC, in all, the changes affected ~10 total lines > of code. > > Is this something that should be looked into? > > Thanks, > > JD_______________________________________________ > platform-dev mailing list* > **[email protected]* <[email protected]>* > **https://dev.eclipse.org/mailman/listinfo/platform-dev*<https://dev.eclipse.org/mailman/listinfo/platform-dev> > > > _______________________________________________ > platform-dev mailing list* > **[email protected]* <[email protected]>* > **https://dev.eclipse.org/mailman/listinfo/platform-dev*<https://dev.eclipse.org/mailman/listinfo/platform-dev> > > _______________________________________________ > platform-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/platform-dev > > > _______________________________________________ > platform-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/platform-dev > >
_______________________________________________ platform-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/platform-dev
