Am 29.01.2013 21:49, schrieb Marshall Schor:
I notice that the top level project (the one you run mvn install on to build
everything) is uimaj-textmarker-parent.
This is different from the conventions of other projects - where the top level
would have been something like:
uimaj-textmarker.
I agree. I chose this layout after the discussion of Richard and you
about this topic, but I do not really have a strong opinion about it.
I would have named the reactor/top level project "uimaj-textmarker", but
there was already a project with this name, the implementation of the
analysis engine and rule inference, which can be renamed to
"uimaj-textmarker-core".
I don't think this is a blocker, but if things are worked on before another
release, it might be good to change this.
I agree :-)
Best,
Peter
The convention other multi-module projects take is to have a top level project,
XXX
have a <modules> statement that specifies the included projects. Among those is
a project conventionally named
XXX-parent
This project is a "pom" project which just has the shared Parent Pom for the
project. In some cases, it's not needed, if the project has no pom "factoring"
that isn't already provided by the higher level poms - the common UIMA parent
pom and the common Apache parent pom.
Most projects have this so they can override the common UIMA parent pom (often,
just until the common UIMA parent pom is updated and released).
-Marshall
