|Ignoring Eclipse build/builders when modifying project structure/classpath [message #550056]
||Wed, 28 July 2010 23:20
| Parag Raval
Registered: July 2010
We have a scenario where the Java project refers to binary and corresponding source Jars.
- <classpathentry kind="lib" path="C:/temp/Bbin.jar" sourcepath="C:/temp/Bsrc.jar"/>
Now, we have added capability to convert this Java project to refer to some source i.e. by removing above classpath entry and adding new entries for referring to src and bin directories and provisioning them.
- <classpathentry kind="src" path="src"/>
- <classpathentry kind="output" path="bin"/>
- package/subpackage/.java file(s)
- package/subpackage/.class file(s)
While converting the Java project (referring to binary) to source by tweaking the .classpath file and adding set of source and corresponding .class files, Eclipse sends set of POST_CHANGE and BUILD events.
Since, we already have .class file(s) for the source that we have provisioned, can we avoid Eclipse builder from kicking-off? If yes, how?
Here, We want eclipse to think it just opened this project and has already been compiled and therefore does not require compilation.
So there are a couple of facets to this problem.
1) How to instruct eclipse that nothing has happened (when eclipse shuts down, it saves the state info and does not need to recompile at startup).
2) How can we accomplish this?
1) Prevent eclipse from telling everyone that something has changed.
2) Still have all the searching running features to continue to work.
[Updated on: Wed, 28 July 2010 23:25]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02011 seconds