Community
Participate
Working Groups
20040310 1. Create a simple program with an error [like: public class Main { public static void main(String[] args) { System.out.println("hi there" + foo()); } private static int foo() { return "test"; } } 2. Run As -> Java Application I would like to be told that this program has an error (perhaps run/debug anyway?) This reminds me when a program was unintentionally broken. Especially important when run (and debug) setup times are long. (this feature is useful in conjunction with bug 45887)
John, we've had this request before, but we dismissed generic (platform) support, since it is unclear if the debug platform can detect relevant errors for contributed debuggers/launchers. I could imagine domain specific handlers that could plug into the platform's lanunching sequence, perhaps, along with launcher domain specific builders. Is that what you had in mind?
*** Bug 11974 has been marked as a duplicate of this bug. ***
I gave an example for the jdt case and have heard others asking for the jdt situation. We heard a similar cdt request at eclipsecon. I don't know if the best solution is to provide a general purpose solution (with handlers) or to do the work in jdt (and provide documentation on how others could do the same)? My proposal would be to provide the jdt specific solution now and see if there is anything can can be generally documented (or in the best case, provided)
Extensions to ILaunchConfigrationDelegate2 will allow for this, and for bug 45887.
Will check for compilation errors in referenced Java projects (For local Java Apps, Applets, JUnit, Remote Java Apps). PDE will need a seperate implementation as they do not inherit from the abstract java launcher (I think). However, we can provide some convenience API for them.
patches submitted to address this bug as well as bug #6400 and bug #45887 at once. Patches attached to bug #45887 Darin, please verify
Applied patch. Need associated preference on the "Java > Debug" pref page to turn on/off prompting.
Created attachment 8672 [details] patch to debug.core moved code to create new NullProgressMonitor above call to preLaunchCheck() to prevent NPE from test suite.
Created attachment 8673 [details] patch to debug.ui created new preferences in IDebugUIConstants
Created attachment 8674 [details] patch to jdt.debug.tests set preference to prevent dialog during tests.
Created attachment 8675 [details] patch to jdt.debug.ui updated status handlers to use new preference added to IDebugUIConstants
Darin, please apply patches for tomorrows test run. Still need to be able to change "I don't ever want to run with compile errors" preference on preference page... please reassign this bug to me.
Applied patch. In addition: * Moved "compile errors" peference to Java Debug (since it will start as a java specific option). * Moved breakpoint detection code to debug platform so all launchers that subclass our abstract delegate inherit the behavior. Reassigning for preference page settings for the following prefs: * IDebugUIConstants.PREF_RELAUNCH_IN_DEBUG_MODE - should be on main debug page * IJavaDebugUIConstants.PREF_CONTINUE_WITH_COMPILE_ERROR - on Java page
Created attachment 8701 [details] preference page patch (debug.ui) changes in DebugPreferencePage and DebugPreferencesMessages
Created attachment 8702 [details] patch (jdt.debug.tests) changes in ProjectCreationDecoration (changed the preference store, and the location of the constant)
Created attachment 8703 [details] preference page patch (jdt.debug.ui) changes to IJavaDebugConstants, IJDIPreferencesConstants, JDIDebugUIPlugin, JavaDebugPreferencePage, and CompileErrorPromptStatusHandler
Darin, please verify 2004-03-19 patches. -thanks
Applied patch.
Verified. We now have a Java specific solution that ties into the ILaunchDelegate2 support (pre launch checks). Others could implement their own solution using the same approach. I will file a new bug to look at ways of leveraging the suppor for other "java like" launchers.
