| >- submitting code to a code review site like Gerrit. Why would you want your build tool to do that? >- generating code (for example, a parsed SNMP MIB that you want as a Java class so you can refer to it easily). There are plenty of plugins to do that. If you want one that doesn't exist, write your own. It's not hard, and means this operation will be encapsulated in a structured, testable, reusable way. If you're generating code in an ad-hoc, specific-to-a-single-project way, you're doing it wrong. >- integration with a tool like Sonar (yes, there's a Maven plugin. You ever used it?). Yep, I've used it. It works fine. >- code coverage analysis (yes, there's a Maven plugin. You ever used it?). Yep, I've used it. It works fine. >- FindBugs style analysis (yes, there's a Maven plugin. You ever used it?). Yep, I've used it, it works fine. >- interesting dependencies on external libraries (to pick an example from Ruby, the json gem was horribly broken at 1.4.2 and generations of projects have varying requirements for json < 1.4.2, json > 1.4.2, and many other worse things. Huh? You can depend on a specific version, a range of versions, or a range with gaps in. You can't depend on two versions of the same library because it's impossible to set the classpath up like that, but that's a limitation of Java, not maven. >- C code (through JNI or anything else, a perfectly reasonable thing to want to do). There are ways to do this, I'll agree it's not pretty. If you want to use another build tool for those projects that include C code that's fair - it should be a minotiry of your projects. >- deployment. Not the appropriate tool for it. |