Summary: | Adding partial compilation for JAVA | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | hutai |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | hutai, philippe_mulet |
Version: | 2.0.1 | ||
Target Milestone: | 2.1 M5 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
hutai
2002-09-23 14:59:00 EDT
What do you call a part ? And what if it needs other files which are comprised in this part ? We do have incremental compilation, which will only compile the set of affected files (once a first full build has occurred). These products do not have it, which may explain why they provide this kind of feature. Note that in 2.1, we want to investigate a filtering approach which could allow you to hide some source files from the Java compiler. Would this solve your problem ? What I mean is when you have a large team project, which couldn't entirely compiled due to some errors in other team member's code. However, you want to make sure that your part of code is compiled. Then you could select your package and only compile on that package. The compiler should automatically compile only the codes which are necessary (including your code and any other code you depend on, but not the whole project). The source filtering may not work in my case. It is because my code may depend on others code (not all, but part of them). Thanks for your comment. Tai So a way to exclude some files from the build would do it, wouldn't it ? |