|Re: How to stop eclipse re-building other projects when trying to run one project [message #1773869 is a reply to message #1773848]
||Thu, 05 October 2017 18:17
| Stephan Herrmann
Registered: July 2009
I know the issues of lots of unwanted build activity from various setups -- much time wasted this way. Meanwhile I typically achieve best results by *enabling* build automatically and ensuring that it only does what I really need. |
In particular, in any maven projects the maven builder typically does more than I need on every save, therefore I remove the maven builder from .project - and ensure that resources are still copied as desired (by removing any exclusions that m2e may have added to .classpath).
At this point, build automatically should be very fast, with minimal transitive rebuilds. If there's anything that needs to be done via maven, I explicitly invoke a maven build for the individual project that needs it when I need it (with build automatically temporarily disabled to be on the safe side).
At the end of it, launching should hardly ever encounter a state where additional building is necessary, voila! :)
As for the particular problem, if you are certain that a launch triggers building of projects that are totally unrelated to any projects referenced by the launch, then this might be a bug worth reporting. Again it will make a difference which builders are involved, since one builder's results may trigger another builder.
Powered by FUDForum
. Page generated in 0.01624 seconds