This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Need to collect the entire dependency tree of a Java Card project, flatten it to a list with duplicates pruned (last duplicate survives) and to pass to debug proxy. Probably needs to be implemented both for Ant tasks and in-IDE use.
Debug proxy command line is now passed entire closure of project classpath, even including any implicit JARs specified by Class-Path entries in the manifest of dependency JARs, as of changeset ce58ee7e9550. Anki: Do we need this data in Ant tasks somewhere, or just for launching the debugger proxy from within the IDE? We have it via project.xml -> build-impl.xsl -> build-impl.xml + project.properties; however, we would need a special Ant task if we need to include implicit dependencies as described above - or we should not include them, and the debug proxy server should read these from the manifests of the JARs we do pass and include any implicit dependencies in the classpath it uses internally. TODO: Need an implementation of SourceForBinaryQuery that can resolve the source files for project dependencies, if the user provided sources when they set the dependency, so the user can actually step through sources in the debugger.
Anki, would still like some clarification here. If it is good enough that the classpath closure is passed correctly to the debug proxy command line when it is started from *within the IDE* then I can close this issue. If we want to somehow start a debug process from Ant, and then attach to it somehow, then I should leave this issue open, and we'll need some Ant task that walks the dependency tree and assembles the same closure string. Would like to get this off my plate if what we have is good enough.
Marking as fixed; if needed from Ant tasks, can be filed separately.