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 129008 - Cannot add dependency on module which is not installed into ide dirs
Summary: Cannot add dependency on module which is not installed into ide dirs
Status: CLOSED INVALID
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-03 13:55 UTC by Tomas Danek
Modified: 2008-03-03 16:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2008-03-03 13:55:11 UTC 
Product Version: NetBeans IDE Dev (Build 200803021202)
Java: 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
System: Linux version 2.6.22-14-generic running on i386; UTF-8; en_US (nb)
Userdir: /tmp/ud
-----------
- create new module
- build nbm
- install this nbm into ide by plugin manager (by default it installs into userdir)
- check in log (or in plugin manager) that module was successfully installed/started
- create another new module -> try to add dependency on installed module -> does not work. To make in work, module has
to be installed into IDE dirs. IMHO it should be transparent to user where module is installed. Aren't caches somehow
involved in this?
Comment 1 Jesse Glick 2008-03-03 14:52:28 UTC 
This is as designed. You can only develop against modules which actually exist in your target platform. The default NB
platform consists of your current NB installation, not its userdir. If you want you can make a special platform
containing extra modules.
Comment 2 Tomas Danek 2008-03-03 16:20:02 UTC 
ok. yup, it makes sense to develop against modules which are directly part of platform. Verified/closed.