| How does Eclipse decide what files need to be compiled? [message #199578] |
Mon, 28 March 2005 15:16  |
Eclipse User |
|
|
|
Originally posted by: wgreene.ptc.com
I have projects with a very large number of files. Apparently, Eclipse
does not use the modified dates for the .java and .class files because,
when I create a new project, Eclipse insists on re-compiling every
file in the project. Which takes a long time. And to make matters
worse, sometimes I'll make a change to a single file, and Eclipse will
perform a complete rebuild, even though it isn't required.
Can someone please explain to me what's going on here and, hopefully,
give me some tips on how to modify this behavior?
Thanks.
Bill
|
|
|
| Re: How does Eclipse decide what files need to be compiled? [message #200107 is a reply to message #199578] |
Mon, 04 April 2005 06:26  |
| Eclipse User |
|
|
|
Eclipse incremental builder is not a make facility, but rather based on a
dependency graph it constructs when compiling files.
Now this requires it to be able to compile all files at least once.
If you are using binaries produced by other tools, then this might be the
cause of your issues, but again it should only occur once ever.
May I suggest you elaborate your usecase into a bug report (against
JDT/Core) so as for us to investigate this scenario deeper ?
"Bill Greene" <wgreene@ptc.com> wrote in message
news:d29om2$uj4$1@news.eclipse.org...
> I have projects with a very large number of files. Apparently, Eclipse
> does not use the modified dates for the .java and .class files because,
> when I create a new project, Eclipse insists on re-compiling every
> file in the project. Which takes a long time. And to make matters
> worse, sometimes I'll make a change to a single file, and Eclipse will
> perform a complete rebuild, even though it isn't required.
>
> Can someone please explain to me what's going on here and, hopefully,
> give me some tips on how to modify this behavior?
>
> Thanks.
>
> Bill
|
|
|
| Re: How does Eclipse decide what files need to be compiled? [message #200144 is a reply to message #200107] |
Mon, 04 April 2005 09:57 |
| Eclipse User |
|
|
|
Originally posted by: wgreene.ptc.com
I just submitted an enhancement request to JDT/Core. You can reclassify
as a bug if appropriate.
After sending my initial post, I happened on the document "Project
Builders and Natures" by John Arthorne. It describes a scenario where
"if a builder is not run for a long time" a full build may be performed.
I'm not sure what "long time" means but, after reading this, it occurred
to me that the behavior I'm seeing may be by design. Are there, in fact,
situations where the Eclipse platform will return a "null delta" to the
Java builder? Is there a way I can cause Eclipse to output some
diagnostic information about project deltas during each build?
Bill
Philippe Mulet wrote:
> Eclipse incremental builder is not a make facility, but rather based on a
> dependency graph it constructs when compiling files.
> Now this requires it to be able to compile all files at least once.
>
> If you are using binaries produced by other tools, then this might be the
> cause of your issues, but again it should only occur once ever.
> May I suggest you elaborate your usecase into a bug report (against
> JDT/Core) so as for us to investigate this scenario deeper ?
>
> "Bill Greene" <wgreene@ptc.com> wrote in message
> news:d29om2$uj4$1@news.eclipse.org...
>
>>I have projects with a very large number of files. Apparently, Eclipse
>>does not use the modified dates for the .java and .class files because,
>>when I create a new project, Eclipse insists on re-compiling every
>>file in the project. Which takes a long time. And to make matters
>>worse, sometimes I'll make a change to a single file, and Eclipse will
>>perform a complete rebuild, even though it isn't required.
>>
>>Can someone please explain to me what's going on here and, hopefully,
>>give me some tips on how to modify this behavior?
>>
>>Thanks.
>>
>>Bill
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04560 seconds
Home