Adam Lally wrote:
On 8/8/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
In the uimaj project's pom, the <parent> element points to itself.
I don't see any <parent> element in the uimaj project's pom.
right - my oops - I was looking at the uimaj-distr pom, not the uimaj pom.
Also, there are two elements defining the javadoc plugin - is this
intentional, or should/can
these be merged?
They are different. One is in <pluginManagent> and just specifies
what version of the javadoc plugin to use. The other is in
<reporting> and has the specifics on javadoc generation when mvn
site:site is run. (This generates the javadocs for the website - I
put instructions for this on the Wiki a while back.) There is yet
another javadoc generation command as part of the assembly process,
that builds the javadocs to be included in the distribution.
If we are heading toward putting things in the Apache / Maven
repositories, should we make
our POMs inherit from Apache-wide poms? I recall some discussion about
this in incubator - creating a parent for incubating projects, for instance.
Maybe but I would prefer to deal with that later. As I recall this is
not a requirement.
OK. In case it is useful, the incubator pom is in the incubator svn:
http://svn.apache.org/repos/asf/incubator/public/trunk/pom/pom.xml and
short discussion can be found here:
http://mail-archives.apache.org/mod_mbox/incubator-general/200609.mbox/thread
It has refs to repositories for snapshots and for "releases".
-Marshall
