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 88669 - 'Create NBMs' target in suite's build.xml does not produce nbms for all modules.
Summary: 'Create NBMs' target in suite's build.xml does not produce nbms for all modules.
Status: CLOSED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ gordonp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-05 19:40 UTC by Karthikeyan Rajeswaran
Modified: 2007-09-06 17:59 UTC (History)
0 users

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 Karthikeyan Rajeswaran 2006-11-05 19:40:52 UTC 
(Filing under 'other' category as this is a build issue).

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 _ gordonp 2006-11-06 19:06:55 UTC 
Assigning to myself. I'll do the modules owned by MPK and open a 2nd issue
for modules owned by SPB.
Comment 2 Karthikeyan Rajeswaran 2006-11-06 19:14:00 UTC 
The original description says:
> (This workaround does not work for highlight module, as the module is not 
> available on the Projects window in the ide).

The above is not correct. Select the main project in the ide, right-click and
select 'Open Required Projects' ; this action opens up all projects  in the
projects window allowing us to run 'Create NBM' on any module/project. So the
workaround does work for all modules.
Comment 3 Karthikeyan Rajeswaran 2006-11-06 22:03:46 UTC 
This problem has been temporarily fixed by listing all the modules specifically
in the 'create nbms' target, as follows:

RCS file: /cvs/cnd/suite/build.xml,v
retrieving revision 1.2.2.2
diff -r1.2.2.2 build.xml
30c30
<         <subant target="nbm" buildpath="..:../makeproject" inheritrefs="false"
inheritall="false">
---
>         <subant target="nbm"
buildpath="..:../configurationapi:../antlr:../gotodeclaration:../highlight:../makeproject:../mobility:../classview:../completion:../modelimpl:../modelapi:../gdb:../update:../modelui:../modelutil:../qnavigator"
inheritrefs="false" inheritall="false">

But buildpath should really be set using the list of modules defined in
nbproject/project.properties which should be the only place where list of
modules are defined.
Comment 4 Vladimir Voskresensky 2006-11-08 11:46:37 UTC 
The solution is just remove target
<target name="nbms">
from suite's build.xml.
As I remember it was overriden because of some NB 5 harness problems.
I think problems were fixed in harness 5u1 and we can use default nbms target.
Comment 5 Karthikeyan Rajeswaran 2006-11-09 00:40:48 UTC 
After removing the 'nbms' target from suite's build.xml, the problem has gone
away .
Comment 6 Karthikeyan Rajeswaran 2006-11-09 00:42:39 UTC 
Closing the issue (as the issue being an internal build issue will not be
verified by qa).