Notes from the People's Popular Anti-Maven Front of Java General MeetingREG: All these years. Maven has bled us dry with convoluted XML files, forced us to respect the Maven way, and made us download the internet at every build. And what has Maven ever given us in return?!
JAVA COMMANDO #1: Standard directory structures?
JAVA COMMANDO #1: Standard directory structures.
REG: Oh. Yeah, yeah. It did give us that. Uh, that's true. Yeah.
JAVA COMMANDO #2: And common build targets across projects. Remember how hard it use to be with Ant, to figure out how to build a new project?
REG: Yeah. All right. I'll grant you, standard directory structures and common build targets are two things that Maven has done well.
JAVA COMMANDO #2: And Declarative Dependency Management.
REG: Yeah. Well, obviously, Declarative Dependency Management. I mean, Declarative Dependency Management goes without saying, doesn't it - everyone wants to do that now. But apart from Standard Directory Structures, common build targets, and Declarative Dependency Management--
JAVA COMMANDO #3: Common artifact naming conventions?
JAVA COMMANDO #1: Code quality reporting
JAVA COMMANDO #2: Yeah, Sonar
REG: Yeah, yeah. All right. Fair enough.
JAVA COMMANDO #4: Enterprise Repositories?
JAVA COMMANDO #2: Yeah, you can actually publish your JAR files without using email, now. They're the ones who came up with that.
REG: All right, but apart from Standard Directory Structures, common build targets, and Declarative Dependency Management, a common artifact naming convention, code quality reporting, Sonar, Enterprise Repositories, what has Maven ever done for us?
JAVA COMMANDO #1: Groovy pom files?
REG: Oh. Shut up!
Check out the original version here.