O'Reilly Book Excerpts: Maven: A Developer's Notebook
Maven Project Reporting and Publishing, Part 1
Building projects with Maven and pulling down all of your needed JARs is so convenient, you might forget that the real goal of Maven is to manage projects, in accordance with widely held best principles. And to manage a project effectively, you have to be able to know what's going on.
This excerpt from Maven: A Developer's Notebook is the first in a two-part series on Maven's reporting and publishing tools. In this excerpt, you'll learn how to use the reports for mailing lists, project members, issue tracking, and dependencies. You'll also see the reports generated for test results and code checking. Finally, you'll learn how to aggregate all of these into a single project quality dashboard.
As with all books in the Developer's Notebook series, you'll get the information in a straightforward, factual style, with the details you need to get the job done. In other words: "All lab, no lecture."
Check back next week for part two, which looks at tracking project changes and releases, reporting releases, and publishing your project website.
Download Part 1 of Chapter 4 from Maven: A Developer's Notebook (PDF, 590 KB).
|
Related Reading Maven: A Developer's Notebook |
View catalog information for Maven: A Developer's Notebook
Return to ONJava.com.
You must be logged in to the O'Reilly Network to post a talkback.
Showing messages 1 through 5 of 5.
-
This is great but ...
2006-01-05 06:49:15 jr@2ft [Reply | View]
Is a new edition of the Developer's Notebook for Maven 2 in the works? I had this book in my hands at a store (yes, a store) but put it down because it didn't address m2
JR
maven 2 lover
-
I really hate to be negative...
2006-01-04 15:22:47 hexghost [Reply | View]
but Maven is one of the biggest hunks of crap that has ever cursed the Java world. What was wrong with Ant? It's perfectly fine for large projects (not that maven's creators have ever made a large project), most of the java world already uses it, and its supported in most of the major IDEs. Instead they had to crap out maven. Incompatible build files with ant, a release schedule that makes Commons look good, and the best thing ever: Total Incompatibility with version 2 to version 1! What an amazing f****ing idea! Seriously, I know you're just whoring this chapter out to get book sales, but look maven creators: shape up and remove this blight to the java world. -
I really hate to be negative...
2006-01-06 05:50:08 madtree [Reply | View]
BTW, Geronimo and Struts are two small projects using Maven instead of Ant. -
I totally disagree with you
2006-01-05 06:04:23 madtree [Reply | View]
I think Maven (especially Maven 2) is one of the best thing that happend to Java world. We were using ant where I work before and here some issues we were facing :
1) For every new projects, we had to copy and paste some typical Ant scripts and change a couple of values according to the project nature. Ant scripts are mostly similar between different projets (compiling, generating doc, packaging, ...). So why loosing times rewriting or copying what is already done. Ant doesn't facilitate reuse.
3) Maven focus on the "what", while in Ant you have to write the "how" and the "what". Why should I have to figure out how to compile, deploy, generate javadocs everytimes? I do that for every projects. Plus, with Ant you have to understand the build script, learn the targets names, you have to *relearn* all this stuff for every projects wich don't use the same standards as you. It can drives you nut sometimes just to build a simple project if the Ant script don't respect some good practices. Why I would want to waste time to understand the build process of a project? I have more important things to do.
3) When you want to add or share new functionnalities, you need to use copy&paste. Again not very practical, with Maven you ship a plugin and it's done. Encapsulation power!
4) No need to check in the jars the projects use in your SCM.
5) Managing dependencies is a lot easier with Maven, especially Maven 2.
6) If you need the power of Ant for custom tasks, it easy to incoporate one in your build using the Ant plugin.
I like to make a comparaison about Ant and Maven using programming paradigms. I refer to Ant has being the procedural approach while Maven is the OO approach, wich addresses a lot procedural issues.
By the way, I am betting Maven will be supported by most IDE in the near future.






I getting the problem in using the repository:copy-jar
the goal that I run is:
maven -DgroupId=activation -Dtype=jar -Dartifact=${maven.repo.home}\activation\activation-1.0.jar repository:copy-jar
error that I got
Execute failed: java.io.IOException: CreateProcess: ssh -l USERNAME_NOT_SET "mkdir -p /activation/jars/; chmod g+ws /activation/jars/; chgrp maven /activation/jars/" error=2
build.properties file :
maven.repo.remote=http://mkeux353:8080/OEMaven/repository, http://www.ibiblio.org/maven
maven.repo.list= OeIfpRepository
maven.repo.OeIfpRepository=*****
maven.repo.OeIfpRepository.username=******
maven.repo.OeIfpRepository.password=*******
maven.repo.OeIfpRepository.directory=/users/maven
---------------
the user name and pass and repository url is correct. because I run artifact:deploy goal successfully. please tell me what is the wrong and we have to specify any more properties in build.properties file.
could you please solve the probem.
thanks and regards,
ravikumar.maddi