mbeckerle commented on issue #66: URL: https://github.com/apache/daffodil-vscode/issues/66#issuecomment-1020292388
I'm ok with a slighly inconvenient "feature" that requires an extra setup step so that schemas become available to the debugger. For example in IntelliJ and Eclipse, if you want to be able to step into source code of a java/scala library, there has to be source-jar info associated with the jar. For eclipse, this requires the extra 'sbt eclipse' step, which explicitly creates a classpath XML file which tells eclipse where these source-jars are and what the classpath is. Not sure how intelliJ discovers these jars, but it doesn't require an explicit step. It must be just searching for them wherever it finds the regular library, and using if found. I can even put breakpoints in the libraries based on java/scala source code. But I can't edit them. So my suggestion is maybe investigate how VSCode for Java works with Java source code for external libraries. How we do it has to work alike (or so it seems to me). Daffodil class path usage is really really similar in intention to how Java classpaths work. In fact some DFDL schema jars will include class files for User-defined functions and layering extensions and validators used by the schema, so Daffodil's jars really ARE java jars that are depending on java standard classpath behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
