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: | Project dependency management wrt gems development | ||
|---|---|---|---|
| Product: | ruby | Reporter: | chaukmean <chaukmean> |
| Component: | Project | Assignee: | issues@ruby <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
Thanks for filing. (TM -> after-6.5, as discussed on ML) |
It would be great if Netbeans support project dependency management as described/illustrated below : - a project B is dedicated to the development of a base library whose gem is named b_lib - a project A is dedicated to the development of an application relying on project B : - there are files from project A that require b_lib - if some ruby files from project B have been modified (but not yet installed through gem install), the project A should see these *newer files* during : - the launch of the project A application - the navigation from a source file from project A to a source file from project B Currently, the launch of project A application only sees files from the installed b_lib gem. Newer version of these files within project B are not seen. Likewise, navigating from a project A source file to a project B source file always open the version corresponding to the installed b_lib gem. Thanks in advance. Chauk-Mean.