5 ms·

I have found the opposite to be true in my experience. IDE's have some level of trouble with most popular Java build tools (Maven and Gradle), while they are qu

I have found the opposite to be true in my experience. IDE's have some level of trouble with most popular Java build tools (Maven and Gradle), while they are quite capable command line tools, and they themselves know how to work well with the IDE's (They each have plugins to create the 'meta' files for the most popular IDE's) What issues have you had with which build tool when using it outside the IDE?

sk5t 11y ago
Same here. Maven works great from the CLI, and Eclipse works great as a dumb-ish consumer of the dependencies and Maven reactor stuff in which to write code. But I don't use Eclipse for real build / test / package tasks, nor is the IDE a very nice place in which to configure the project skeleton.
EdwardDiego 11y ago
IDEA's Maven and Gradle support is pretty good. I haven't had to use any Maven plugins to generate project files for an IDE since IDEA 7. But yeah, mvn and gradle are the definitive, the IDE support is a nice to have.
- mavelikara 11y ago
  IDEA's native Gradle support is excellent. I haven't had to use Gradle's IntelliJ plugin (the Gradle bit that generates the IDE files) for at least two years now. All I have to do is (on Mac OS X): open -a /Applications/IntelliJ\ IDEA\ 15\ CE.app build.gradle At work, we have a Gradle project with 346 submodules. We have about 200 engineers working on the codebase. Gradle/IDEA combination works well beautifully. There are a few rough edges, especially when one uses custom source sets. IDEA 16 is going to get better support for that [1]. [1]: http://blog.jetbrains.com/idea/2015/12/intellij-idea-16-eap-starts-the-faster-release-cycle/ http://blog.jetbrains.com/idea/2015/12/intellij-idea-16-eap-...
reitanqild 11y ago
> IDE's have some level of trouble with most popular Java build tools (Maven and Gradle) Can't speak for gradle but Netbeans has worked excellent with Maven for years. Idea seems to work nicely as well (I haven't used it much for the last few years but my coworker across the table seems to like it with Maven as well.) As for eclipse I haven't used it regularly since 2012 so I don't know.

sk5t 11y ago

Same here. Maven works great from the CLI, and Eclipse works great as a dumb-ish consumer of the dependencies and Maven reactor stuff in which to write code. But I don't use Eclipse for real build / test / package tasks, nor is the IDE a very nice place in which to configure the project skeleton.

EdwardDiego 11y ago

IDEA's Maven and Gradle support is pretty good. I haven't had to use any Maven plugins to generate project files for an IDE since IDEA 7. But yeah, mvn and gradle are the definitive, the IDE support is a nice to have.

mavelikara 11y ago
IDEA's native Gradle support is excellent. I haven't had to use Gradle's IntelliJ plugin (the Gradle bit that generates the IDE files) for at least two years now. All I have to do is (on Mac OS X): open -a /Applications/IntelliJ\ IDEA\ 15\ CE.app build.gradle At work, we have a Gradle project with 346 submodules. We have about 200 engineers working on the codebase. Gradle/IDEA combination works well beautifully. There are a few rough edges, especially when one uses custom source sets. IDEA 16 is going to get better support for that [1]. [1]: http://blog.jetbrains.com/idea/2015/12/intellij-idea-16-eap-starts-the-faster-release-cycle/ http://blog.jetbrains.com/idea/2015/12/intellij-idea-16-eap-...

reitanqild 11y ago

> IDE's have some level of trouble with most popular Java build tools (Maven and Gradle) Can't speak for gradle but Netbeans has worked excellent with Maven for years. Idea seems to work nicely as well (I haven't used it much for the last few years but my coworker across the table seems to like it with Maven as well.) As for eclipse I haven't used it regularly since 2012 so I don't know.