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 88733 - 'Create NBM' target in suite's build.xml does not produce nbms for all modules.
Summary: 'Create NBM' target in suite's build.xml does not produce nbms for all modules.
Status: CLOSED INVALID
Alias: None
Product: cnd
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-06 19:10 UTC by _ gordonp
Modified: 2007-04-02 21:20 UTC (History)
2 users (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 _ gordonp 2006-11-06 19:10:56 UTC 
Note: This is an intentional duplicate of 88669. I'll fix the modules
owned by MPK as the fix for 88669. Please fix the modules owned by SPB
with this IZ.

It would be nice if the nbms were signed (there is a related issue about
that). However, if its more than minimal work then it can be deferred
until after FCS (I'm not really sure whats involved, but Kartic
(krajeswaran@netbeans.org) can probably tell us.

Steps to reproduce:
- Load the c/c++ pack build project in the ide.
- Select 'c/c++ build system' , right-click and select 'Create NBMs'.
Only org-netbeans-modules-cnd-makeproject.nbm and org-netbeans-modules-cnd.nbm
are created under suite/build/updates directory; all the 15 module nbms should
be created.

Workaround: Select individual projects, right-click and select 'Create NBM'.
This creates the nbm for that module in that module's build directory. (This
workaround does not work for highlight module, as the module is not available on
the Projects window in the ide).
Comment 1 Karthikeyan Rajeswaran 2006-11-07 22:52:21 UTC 
This is a problem with the master build.xml (in the suite) and is not an issue
with the individual build scripts. Therefore this iz record can be closed and
the problem can be tracked in 88669.
Comment 2 _ gordonp 2006-11-08 00:02:27 UTC 
Based on Karthik's comments...