Scenario:
Project A, B and C is dependent on say X.jar. I am updating the X.jar where those files are only related to Project A. But eclipse builds all the three projects,if the jar gets updated.
Problem: Eclipse has all the dependencies graph(I believe) and why it is behaving like this?
If its build only project A then lot of time will be saved.
Worst case scenario will be when JDK changes (I am seeing this also as a JAR changes),so only the files which are compatiable with the latest versions and it dependencies shuld be built.
It should try for the incremental build . Any thoughts guys......
Friday, November 30, 2007
Subscribe to:
Post Comments (Atom)
1 comment:
Thala Nice thought.. It may be because the IDE's (not even Eclipse) stores what class is dependent on what project.. it works on the dependencies that is provided in the class path by us...
May be future IDE should be built on AI..... So that Even When JDK changes only the changed API dependent classes are build.... but what about the resources that is required for this.... Now even Vista requires a 2 GB Ram Machine... to work normally...
What Say Ya..
Post a Comment