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

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

jdavidb
  (email not shown publicly)
http://voiceofjohn.blogspot.com/

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Friday January 18, 2008
11:11 AM

First experience with Maven: sour

[ #35421 ]

Don't just dump a pom.xml file in the top directory with no other documentation than a LICENSE.txt. You're lucky I even know that pom.xml refers to Maven at all, and it's only by a miracle that I know I need to type "mvn" rather than "maven" to run maven.

I'm somewhat reasonably intelligent so I assumed I was going to type the mvn command followed by some optional build targets, so I did some reasonable things to find documentation of those build targets. There was no documentation in the downloaded package, nor does documentation appear to exist on the website. Thus far, this is the developer's fault.

So, I just ran a straight mvn. I got an error that I need to specify a build target (a "goal" in maven parlance), with a suggestion that I try "install," which is scary. That's it.

Apparently if I want to know what build targets are available, I'm going to have to look at pom.xml myself. The whole point of XML is to make files which are easy for software to read. So mvn ought to do this for me. I don't know how to read pom.xml; I've never read it in my life, and to be honest I need to spend my time learning ant's xml format for my job, thank you very much. And when I do discern what build targets are available, odds are I'll have no pointers as to which are standard, which are rare options, which are old unsupported junk, etc.

Take advantage of XML and tell me what's in it.

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.
  • You mean a big, bloated tool written in a big, bloated language for big, bloated projects by less than average developers who can't write a line of code without their precious intellisense isn't any good?

    Shocking.

    • Geez, it's a wonder anyone gets anything done with that language, much less makes any money.
  • Your experience mirrors my own [happygiraffe.net].

    In other “maven sucks” news, I tried to help out somebody in my office on a Maven project today. I discovered that web development has turned into:

    • Change a line in a file in Eclipse
    • Run Maven to build a package and install it to the local repository (~/.m2).
    • Run Maven to build a war file and run "jetty":http://www.mortbay.org/ with it.

    This whole process takes around 3 minutes. There's nothing like “edit page / hit refresh”. It's taking

    • I had been looking at it and I am starting to see a lot of areas Maven can suck you into a big black hole. I think I will put the book down now.