Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: When I change the native library location entry of a jar library in the classpath of a project, no recompilation is necessary. Eclipse triggers a project recompilation. More information:
Sorry but how are we supposed to know that the jar is the exact same ?
(In reply to comment #1) > Sorry but how are we supposed to know that the jar is the exact same ? > It's not the jar, that has changed (what I am talking about), but just the native library location. The jar remains the exact same. And a native library doesn't need a recompilation. Marvin
Do you have an example ? I just change the 'native library location' of a jar & it caused an incremental build. Starting build of 278849 @ Mon Jul 06 10:47:43 EDT 2009 Found source delta for: 278849 Clearing last state : State for 278849 (#1 @ Mon Jul 06 10:46:52 EDT 2009) INCREMENTAL build Recording new state : State for 278849 (#2 @ Mon Jul 06 10:46:52 EDT 2009) Finished build of 278849 @ Mon Jul 06 10:47:43 EDT 2009
(In reply to comment #3) > Do you have an example ? > > I just change the 'native library location' of a jar & it caused an incremental > build. This is exactly, what I was talking about. No recompilation (incremental build) is necessary here. If I just change the native library location and the jar remains the same (just as everything else in the build path) like you did, no incremental build should be triggered. Marvin
But every resource change triggers a full or an incremental build. We must check to see what has changed with the jar file. No source files are recompiled as a result of this change.
Verified for 3.6M1
