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 47790 - [40cat] How to compile a directory
Summary: [40cat] How to compile a directory
Status: RESOLVED DUPLICATE of bug 45888
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-24 13:13 UTC by meliandra
Modified: 2004-08-30 08:57 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description meliandra 2004-08-24 13:13:50 UTC
[ BUILD # : 200408191352 ]
[ JDK VERSION : J2SE 1.5.0 ]

I miss the functionality to compile a complete directory structure.

NB 3.6 it's possible.
Comment 1 Petr Hrebejk 2004-08-24 16:40:15 UTC
This option is gone with the new project system. Just compile the
whole project. At will take care of compiling only classes which have
to be changed. If you want to rebuild the project use the clean and
build action.

Comment 2 Jesse Glick 2004-08-25 00:02:52 UTC
Incorrect resolution.
Comment 3 Jesse Glick 2004-08-25 00:03:04 UTC

*** This issue has been marked as a duplicate of 45888 ***
Comment 4 meliandra 2004-08-25 09:16:23 UTC
That's not working for me. 
In our project we are working on at the same time on different
subprojects.
It happens that somebody put uncompilable code into cvs.
So if I just have to compile the packages from my subproject I have to
select every single class because the project itself isn't compilable.
Comment 5 Jesse Glick 2004-08-25 19:53:14 UTC
Hence issue #45888 being open.

BTW if your colleagues commit uncompilable code to CVS, you have every
right to scream at them and make them fix it right away.... see also
nice tools like Cruise Control that let you do continuous builds if
you have an Ant script to run.
Comment 6 meliandra 2004-08-30 08:57:58 UTC
It's no problem with my direct team colleagues. But there's sometimes
a problem with sources from a different team that's working on a
different location 400 km away.

It's similiar like programming different modules. They don't use our
code and we don't use there code. Our part of the application runs
without their changes. But the whole code is in one package structure.