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.
  • ...there's just so much there it's overwhelming. We currently use it to help minimize Ant cruft because with, after some initial configuration, a fairly short XML file Maven will do quite a bit for you, allowing you to declare separate pieces of your application (which can be built as separate JAR/WAR/EAR files) and the dependencies each has. It also has hooks to run all your tests, generate a ton of different types of reports (code coverage, style checking, ...), and generate a functional website for your project. It does impose some restrictions on you (breaking up your application into separate projects because project == JAR) but IMO these have other benefits that make them worthwhile.

    The main problem is that Maven ignores the "make easy things easy" that attract a lot of people to projects. I had a really hard time getting started with Maven because as you noted there's lots of abstract talk about the framework but not enough about what you can do with it. (Although this was about a year ago and the docs may have improved since.) Articles from OnJava [onjava.com] and DeveloperWorks [ibm.com] helped a bit. But as with a lot of frameworks there 's just too much internal docs and not enough end user docs.