2 ms·
The main problem I have with Eclipse and heavy IDE's in general, is their build systems rarely play well with the standard, standalone build systems such as mav
by sixbrx 13y ago
The main problem I have with Eclipse and heavy IDE's in general, is their build systems rarely play well with the standard, standalone build systems such as maven or sbt, which are already necessary and sufficient with the latter even doing incremental building already. These standard build systems are a requirement because they track external dependencies and not everyone in the group can be assumed to use the same IDE anyway.
Sure there are plugins to "integrate" these build systems, but I've wasted too many hours futzing around with keeping the external build system in sync with their Eclipse plugins (many times having to recreate projects altogether to get past some sorts of corruption). Anybody who's had to pollute their poms with Eclipse specific config after a lot of research because of the "Plugin execution not covered by lifecycle configuration" problem will know what I mean. Don't get me started with sbt integration.