Phil Steitz wrote:
Henri Yandell wrote:
First few commit messages bounced on this btw, until I fixed that up.
It's a maven2
Hen,
Can you enlighten the rest of us as to what this is for and what, if
any, implications it has on how we address maven2 artifacts originating
in jakarta projects?
Phil
<snip/>
The purpose of having a parent pom is to reduce the amount of
information you need to put in the pom of a specific project.
It also makes sure that all projects us the *same* information for
certain things. These things are put in the parent. An example of this
is which plugins *all* projects must use. Each project can then add more
plugins if they so desire.
Now I know some of you are preparing to throw in arguments about how we
tried to do this with Maven 1 and it failed. Before you do there is one
crucial difference. In Maven 1 the parent had to reside somewhere within
the same file system as your project. In Maven 2 the parent pom is
published to a Maven repository. It is then downloaded like any other
artifact by Maven automatically. So there will be no need to check out
jakarta-build from svn and putting it in the exact correct location on
your own machine.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
