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 174180 - Reloading classes from several project modules
Summary: Reloading classes from several project modules
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-09 05:06 UTC by sky123
Modified: 2009-10-14 15:21 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 sky123 2009-10-09 05:06:01 UTC
Currently Tomcat supports classes reloading, but from only single web-project. Large projects could consist of several
sub-projects - which means we have several /classes folders on different locations, which are belong to different
locations. Finally, when building war, these subprojects form jar files in web-inf/lib. But during development it is
very unneficient to build/redeploy whole project every time (takes about 10 min). It will be very convinient if Netbeans
will support multiple class locations (and maybe web-resources also) and handle class reloading, like Sysdeo tomcat
plugin for Eclipse does.
We tried to use DevLoader which is coming with SysDeo plugin, and we got a class loading from different locations, but
we haven't got classes RE-loading when compiling them from Netbeans. Only main project classes are reloaded, but not
subprojects. We guess that IDE should inform Tomcat that classes in other loactions were changed.