Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Command Line debugging fails to trace back external classes #1174
Refer to Issue #882 to see changes made for command line debugging. (See ignored test testbed/test/cruise.runtime.RuntimeErrorOutputTests.ExtendsClassExternal())
Command-line debugging is meant to be able to trace back to other Umple files that caused an error, even if they are not the files that contain the main function where the error occurred. In order to do this, while generating the Java code Umple creates a bunch of "uncaughtExceptionHandlers" in the Java file that contains the main function. Unfortunately, if a Umple class extends another (abstract) class from a file using the command "external", then it assumes the file is already precompiled and does not attempt to generate the "uncaughtExceptionHandlers" for any functions within that file. If the external file has errors in it the executing Umple file would not be able to display on the console the source of the error.
Minimum Steps to Reproduce
I'm not sure if this is possible to implement, and even if it is I'm not sure if it is worth the time to implement. I have left this known issue here for now.