1 2 Previous Next 16 Replies Latest reply on Oct 29, 2010 11:40 AM by wangliyu Go to original post
      • 15. Re: How I loathe thee maven.
        swd847

        Steven Boscarine wrote on Nov 30, 2009 18:15:

        The bottom line is that eclipse and maven do work well together.  There are hundreds of really useful plugins for maven, which make the initial learning curve very much worth it.  I have saved a lot of time by moving to maven. 


        I couldn't agree more. My favorite thing it does is download to source and javadoc for every library and set them up properly in eclipse, that alone makes it worth putting up with its little annoyances IMHO.

        • 16. Re: How I loathe thee maven.
          wangliyu
          I *hate* Maven (even with latest greatest mighty Maven3.0GA), I think JBoss/Seam/Weld should provide alternative ways to build the system, not just go Maven(seems hibernate 4 goes away from Maven, finally find sanity there), if anybody wants Non-Maven build tools for Weld project, please vote against Maven, OK, I'll list the problems Maven introduced to me:

          1, Download, JBoss has several repos, the repo that in the generated CDI project pom.xml is always broken, and even if you add the right one (I think, based on the JBoss "official" wiki), it still missing some (for example the arquillian alpha3 broken too).

          2, If I have some local jars (for example WebLogic's jars, some JCA jars from different vendors, Jmeter doesn't even in any repos), you have to either manully install them into the local or remote REPOs, or you have to use "system" scope, either way it's hard (imaging you have more than 30 local jars in the same lib folder and you need to put into POM.xml one by one, I would rather just include lib/*.jar).

          3, Maven have lots lots plugins, most are half-baked, for example, I have module that have 2 test folder, one is for unit test, one is for load testing, Maven doesn't like, some module doesn't have test (for example the application integration test support module, it used for support the testing) and maven doesn't like it, I have 2 source folders(one for JDK1.4, and another for JDK1.6), Maven doesn't like, the resource/compile plugin can't support compile with different source level.

          4, what's the purpose to put the parent version# in each module's pom.xml, I still don't get that, seems Maven3 said it doesn't requires, I haven't test that yet.

          4, Maven claim that it support multiple modules, it doesn't, for example, I have arquillian helper class for packaging the test.jar, it should be put in the common modules and shared by other modules, Maven doesn't like, I have to either put to the runtime code so share with other modules or I have to copy it to any modules that needs it. and also, if you build the secound module, you have to manully goes in modules that it depends on and build them one by one.

          5, Maven said if you are not follow the maven rules setup the proj, you are stupid moron, I don't think I'm stupid moron and every project setup for a reason, there is no "one thing fits all". Weld should give user more options to pick.

          I'm testing with Gradle now, see if that can helps me.
          1 2 Previous Next