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 66938 - Fine-grained setting of projects which should not be built
Summary: Fine-grained setting of projects which should not be built
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Zezula
Depends on:
Reported: 2005-10-17 10:41 UTC by Roman Strobl
Modified: 2011-08-31 14:06 UTC (History)
1 user (show)

See Also:
Exception Reporter:

screenshot (27.43 KB, image/png)
2005-10-18 09:10 UTC, Milan Kubec

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Strobl 2005-10-17 10:41:48 UTC
Let us have following real-life scenario: suppose we have 11 large projects with
inter-dependencies. These dependencies are quite complex (e.g. 4 dependencies on
other projects in average). In this case building the main project takes around
60 seconds on a slow machine even if just a single line of code is changed - it
is necessary to traverse all the build scripts and that takes time.

To solve this problem, it would be nice to have a way how to omit some of the
projects from build process. A typical example are libraries which do not change

There exists a checkbox in Libraries section of project properties. This
checkbox could be available in every dependent project so that library projects
can be easily removed from the build process and would have to be built manually
in case there are any changes. This would lead to a fast build of commonly
edited projects.
Comment 1 Jesse Glick 2005-10-17 23:34:55 UTC
Probably INVALID:

1. You can already avoid building subsubprojects of a subproject (in their own
properties dialogs).

2. If you wanted to build some, but not all, subprojects, you could simply
override the deps-jar target to build the ones you cared about. Does not seem
like a general enough requirement to justify a special UI to me.
Comment 2 Milan Kubec 2005-10-18 09:08:38 UTC
Jesse, I think that this is not so invalid.
ad 1) It would require to know all dependecies between all subprojects (in fact
dependency tree)
ad 2) This use case came out of people that are not familiar with our underlying
infrastructure at all and forcing them to learn how it actually works might end
up in giving up on NB from their side.
Regarding UI: I don't think that the checkbox needs to be in every project it
would just make it harder to find. IMO better would be to place the check box
next to each project in the list of libraries the project depends on. See
Comment 3 Milan Kubec 2005-10-18 09:10:30 UTC
Created attachment 26062 [details]