3 ms·
IDE's can be fiddly, and anyway I don't think it's good to depend on an IDE for building. The project could have been set up instead with the "Maven wrapper"(1
by sixbrx 5y ago
IDE's can be fiddly, and anyway I don't think it's good to depend on an IDE for building.
The project could have been set up instead with the "Maven wrapper"(1) which provides "mvn.cmd/sh" scripts at the top level of the project to fetch and run the proper Maven. So after cloning the project, all you have to do is set a proper JAVA_HOME if it's not already set, and then do "./mvn clean package" at the top of the project to do a complete build. The IDE's will then set themselves up properly if you import the project as a Maven project, and will sync with changes to the Maven pom.xml whenever it changes (Intellij does at least). That's really hard to beat.
(1) https://github.com/takari/maven-wrapper https://github.com/takari/maven-wrapper (Being integrated into Maven itself soon).
- the_gipsy 5y agoI can (and often do) build from CLI, that is much smoother. I tried using vim on java, but honestly you need an IDE for all the constant code generation and incessant fixups by mouseclicks that are needed. Vim+coc is more than enough in the other languages that I use.
- dboreham 5y agoYou're living in a parallel universe from the rest of us. IDE isn't necessary (and positively odd) for building Java.
- the_gipsy 5y agoYou do need to be able to build from IDE when you set breakpoints to debug.
- Hackbraten 5y agoYour IDE should be able to connect to any JVM that has been launched with the proper VM arguments. We occasionally do remote debugging at work. It’s just a matter of copy/pasting the correct JVM incantation into the IDE.
- Hackbraten 5y agoI feel the parent comment was about editing, not building.
- vips7L 5y agoHe is. VsCode (or any editor) + the Eclipse Language Server is more than enough. His complaints about debugging is because he doesn't know about attach debugging.