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: | Target platform cannot include external clusters | ||
|---|---|---|---|
| Product: | apisupport | Reporter: | Jiri Prazak <bohemius> |
| Component: | Project | Assignee: | rmichalsky <rmichalsky> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | asotona, gsporar, matteodg, mryzl, tomwheeler, wadechandler |
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
Jiri Prazak
2006-08-21 14:11:23 UTC
It could be a lot of work to implement this, TBD. I don't know if we have any
plans to do any serious work on apisupport.
The recommended approach, detailed in harness/README ("suite chaining"), is to
create a new platform containing both the core NB platform/IDE plus your extra
cluster(s), and set that as the target platform for your module development. You
should be able to easily set up an Ant target to recreate this platform on
demand, perhaps automatically as part of the build of your module, so no extra
steps are required during development. Re. Javadoc and source associations: this
should work if you add appropriate entries to the NetBeans Platform Manager for
your target platform. You would need to include both the nb.org CVS root (for
the core platform), and the suite dir for mobility.
Let me add some more arguments to push this issue. Now the only CLDC Pack consists of 19 independent modules (source roots) so setting up the platform sources manually for Mobility is 19-times more complicated then setting the platform sources for all the other NetBeans modules. And this will be required for all develpers that we (or any other other Packs) want to persuate to contribute to NetBeans. By skipping this manual source-roots setup we dispose the features like debugging, javadoc, goto-sources. Another important use case for us is ability to share some modules between two Packs. Currently we plan to provide some mobility core that we be used in both packs: CLDC Pack and CDC Pack. NetBeans architecture already contains this pattern however Apisupport achitecture does not allow to do so. NetBeans module and clusture architecture is already layered and allows various types of dependencies however this is allowed only to a listed set of modules and everything else is treated as an exception. One close analogy: Would it be acceptable way for any other NetBeans project type to depend on a library project by copying the library jar into a lib/ext of the JDK and to force developers to manually setup the source roots of all the libraries inside the Java Platform Manager? asotona: your modules should all be placed into one suite, probably. There is no particular reason why you cannot build any number of "packs" from a single suite. Also re. source setup, remember that NB Plaf Mgr associates sources per whole *suite*, not per module, so it does not matter if you have 19 or 190 modules in that suite. BTW nb.org source layout is indeed an exceptional case for historical reasons that we plan to resolve at some point in the future. Cannot do it now because there is zero progress from build masters in defining what Ant entry points they require. Again, this is a reasonable feature request, but I don't know if we have time to spend on it. For now I would rather ensure that you are using the correct workarounds. Currently it sounds like you are not. *** Issue 114389 has been marked as a duplicate of this issue. *** I have a module suite for visual-vm and a module suite for NetBeans, however I'm having trouble getting both suites to share modules that I have developed. You can view it as If I have 'common' 'visual-vm-client' and 'netbeans-client' and I want: visual-vm-suite to contain 'common' and 'visual-vm-client' netbeans-suite to contain 'common' and 'netbeans-client' This doesn't seem to be allowed as the IDE (6.1) keeps wanting me to change the association. This is horrible, and I was pointed to this bug as the root of the problem. With the release of VisualVM this seems to be a bigger issue as I can't have a suite for both NetBeans IDE and VisualVM (currently) Probably WONTFIX. The harness is too complicated already and we should not make it worse. Complex scenarios are probably better handled by Maven. Suite chaining already works for the case that you are building on a derivative platform created by someone else. In case you in fact "own" all the non-NB source modules, you do not even need suite chaining - you can create multiple products out of one suite using simple configurations (i.e. sets of Ant properties), which may have direct GUI support in the future. Jesse, Re. "you can create multiple products out of one suite using simple configurations (i.e. sets of Ant properties), which may have direct GUI support in the future." Is there any more information on this? Is there a tutorial or some documentation some where? If not, can you post the steps here so that Tom, me, or someone can make some entries in the Dev FAQ? Thanks. Re "Is there a tutorial or some documentation": I plan to create sample project with such a setup (based on info from Jesse), however I will not get to it before code freeze of 6.5. Of course I'll appreciate if anyone wants to try it sooner. already solved by issue #152960 |