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 90044 - Project dependencies are built several times
Summary: Project dependencies are built several times
Status: NEW
Alias: None
Product: javaee
Classification: Unclassified
Component: EAR (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P2 blocker with 1 vote (vote)
Assignee: issues@javaee
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2006-11-25 20:05 UTC by Kirill Sorokin
Modified: 2007-10-19 18:31 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 Kirill Sorokin 2006-11-25 20:05:19 UTC
I have an enterprise application which consists of two web modules. Each of them
has a java class library project as its library. When I select Clean and Build
for the whole enteprise application, the java class library project gets built
twice.

The second time is definitely excessive.

--
I'm working with 

NetBeans IDE Dev (Build 200610231500)
1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b104
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251
Comment 1 Kirill Sorokin 2006-11-25 20:06:01 UTC
Well.. A performance issue obviously. ;)
Comment 2 Martin Adamek 2007-01-08 08:47:01 UTC
Reassigning to EAR project.
Comment 3 Kirill Sorokin 2007-01-08 13:04:36 UTC
After a second thought.. Not really a defect, but an enhancement request.
Comment 4 robdaemon 2007-10-19 18:31:05 UTC
I would argue that this is not an enhancement but a bug.  A bug that severely limits the use of NetBeans on a
large-scale project, at that.

I work on a large scale enterprise application with about 30 modules with varying dependencies on each other.  When I
build the product, all of the modules are built several times.  This build process takes over 25 minutes, when it should
take less than 5!

This should be a matter of setting an ant property after the build of a module is successful, and only calling build on
the dependent module if that property is not set.

This is not just a J2EE bug, but an Ant build bug.