robert burrell donkin wrote:
i use 1.0.2 but when i run
"maven multiproject:install"
i get:
"The build cannot continue because of the following unsatisfied
dependency:
jaxmexs-0.6-dev.jar (try downloading from
http://ws.apache.org/jaxme/xs/)"
maven:multiproject fails in a similar fashion. is it necessary to build
each project separately?
Hi all,
I did a fresh install of maven 1.0.2 and a fresh checkout of the MAVEN
branch and I think I found where the problems are.
First IMHO multiproject plugin won't suit our needs. If we make use of
the reactor through maven.xml things go smooth. Second, the groupId's
where wrong. I think there is a bug in eclipse's maven plugin. When you
are inheriting a pom and you don't specify the groupId it makes a guess
on it (being the same as the artifactId). So I'd suggest not to inherit
this element. I think it is the way maven knows about the build order.
And last, I don't think it is a good idea to have the top-level project
inheriting the same pom and properties as the other projects. IMO this
is why it is suggested to have a common-build pom for the subprojects
and have a top-level project with no sources. With maven-plugins this is
how it is done. An inmediate benefit for us is that we can specify a
different maven.docs.src until the user docs of the top-level projects
are converted.
I've also added a sourceModifications for Java5REHandler. Probably other
source modifications are needed. Currently I only have jsdk 1.4
installed so I am not sure. I will install 1.3.2 today and have a look.
Another question. Do we prefer to set the goals of all subprojects in
the project.properties or do we want the reactor just to execute goal
build which will be defined in common-build/maven.xml?
regards,
nacho
PD: I'll try to investigate why we need commons-jelly-tags-fmt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
