5 ms·
By "special compilation tool chain" do you mean Maven? That's not special, that's standard. On the contrary, I was put off by the build example for Jodd needing
by vorg 11y ago
By "special compilation tool chain" do you mean Maven? That's not special, that's standard. On the contrary, I was put off by the build example for Jodd needing Gradle to build, rather than Maven. Gradle and its bundled scripting language are heavyweight, which goes against the whole idea of micro-framework philosophy as described in the article, i.e. "much of the functionality wrapped in those [legacy] libraries is no longer really needed for most projects. Micro frameworks are an attempt to address this."
- dikaiosune 11y agoTo be perfectly honest, I was misremembering the information from this page: http://www.ninjaframework.org/documentation/getting_started/setting_up_your_ide.html http://www.ninjaframework.org/documentation/getting_started/... As I had previously recalled, Ninja's SuperDevMode involved a bunch of bytecode manipulation or something, but that was obviously incorrect. Re Maven vs. Gradle, I HATE XML with a burning, undying passion. It's just my personal holy war, and while I quite like Maven, I moved to Gradle a while ago to cut out the main source of XML anguish in my life. Of course, a quick google indicates that that is changing too: http://www.infoq.com/news/2015/03/maven-polyglot http://www.infoq.com/news/2015/03/maven-polyglot I do like me some YAML. Realizing that my early-morning phone comment was from half-memories and out-of-date information? Not so much :).
- tomjen3 11y agoUsing Maven for anything but the dependency resolution part feels like coding XML stylesheets. The dependency resolution is awesome, but buildscripts needs to be expressive, do a lot of dirty work and still run fast. Maven does none of that.