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.

Bug 147841 - Project dependency management wrt gems development
Summary: Project dependency management wrt gems development
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@ruby
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-22 10:16 UTC by chaukmean
Modified: 2011-01-28 20:12 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description chaukmean 2008-09-22 10:16:22 UTC
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.
Comment 1 Martin Krauskopf 2008-09-22 10:20:27 UTC
Thanks for filing. (TM -> after-6.5, as discussed on ML)