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.
Summary: | Chaining suites - associated sources are not available | ||
---|---|---|---|
Product: | apisupport | Reporter: | pzajac <pzajac> |
Component: | Project | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | tboudreau |
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 89629 |
Description
pzajac
2006-03-08 12:28:09 UTC
Similar and probably related. Suite application S2 is built on suite application S1 taken as platform for S2; S1 is built on NB-5.0 platform. Navigation and debugging work fine between modules of S2 or between modules of S2 and modules of NB-5.0 platform but not between modules of S2 and modules of S1. Navigation is possible between modules of S1 or between modules of S1 and modules of NB-5.0 platform. S1 module sources are not part of S2 project suite despite being mounted in the source tab of the platform manager. Seem to have a fix. SFBQ was assuming that the module JAR would be in its originally built location, or at least that modules/ would be beneath a dir called "cluster" - which is true for $suite/build/cluster/modules/$cnb.jar, but not for a typical derived platform where it might be $plaf/$app.name/modules/$cnb.jar. Relaxed the check a bit so only the modules/$cnb.jar part is matched, and not the cluster dir name. Checking in SourceForBinaryImpl.java; /shared/data/ccvs/repository/apisupport/project/src/org/netbeans/modules/apisupport/project/queries/SourceForBinaryImpl.java,v <-- SourceForBinaryImpl.java new revision: 1.11; previous revision: 1.10 done |