Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
    • +10; Maven suffers from the fate of other ambitious development tools:

      1) It imposes its own worldview on How Things Should Work (e.g., only one source tree per 'module') that require you to develop, package or deploy differently.

      2) Hand in hand with that, it's a "drink the kool-aid" project -- you need to know how things work to figure out how they should work. For instance, Ant has a simple way to ask "What targets can I run with this buildfile?" Maven has no useful implementation of such a thing (the list of 'goals' is so long it's useless), so if you're encountering it for the first time you need to take on faith that the default will do something useful, or that the project that's using Maven has documented what you should do. But even then you're being led to actions rather than discovering them.

      3) Documentation blows, so when something doesn't work like you'd expect (which, if you haven't drunk the kool-aid, is fairly frequent when you start) it takes far longer than it should to figure out why.

      Plus, one of its most-touted features (dependency management for libraries) has never seemed very useful to me.

      Chris
      • They make no bones about 1 and 2. That is even in the book I am reading on it. So what? Everything imposes its own world view at some level. The book is good which is what got me wondering.
        • The "so what" happens when you want to something outside their proscribed worldview. I don't think tools should impose constraints like that, but YMMV.

          And, of course, all this just applies to the one implementation; there's nothing that says a copy needs to copy all the warts :-)
          • And, of course, all this just applies to the one implementation; there's nothing that says a copy needs to copy all the warts :-)

            That is what I was thinking as well.