On 7/3/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Though I read on a separate thread on this list
(http://www.nabble.com/Top-level-POM-behaviour-t1825699.html#a4980080)
that doing a module based build is not working for separated projects.
That is why I didn't put a modules section in the parent project.
Here's the quote from Alexandre:
---- begin quote ----
Modules are meant to be built from the top project so you can work on
all of them at the same time. Don't try to build them separatly
because it won't work. If it's not what you want and you prefer
compiling each project separately, you should stick to normal SNAPSHOT
dependencies.
---- end quote ----
In our case, each project may have a separated build: wicket-spring is
a self contained project with its own website etc.
Am I not grokking something here? Should I add a modules section to my
parent project?
I'm no expert, I can only speak from what I have made work.
The problem is that Continuum doesn't do a multi-module build.
If you load in a pom that contains modules Continuum will create a new
project, one for each module definition. I'm not even sure I want
Continuum to do a multi-module build as I'd rather it rebuild only the
parts that require rebuilding because of a change rather than the
entire system. I haven't analysed this enough to work out what makes
sense.
I have not found adding modules to the pom to be a problem, except if
you try to use ${project.version} in the dependency management
sections because the dependency management section will get bound to
the timestamped snapshot version of the parent project's build. Since
the other modules are not being built at the same time you will get
errors that maven can not locate the modules with the same timestamped
snapshot version to download.
It was simple to resolve by replacing ${project.version} with -SNAPSHOT.
Then you have two choices, both of which will work fine in building
your application.
You can build from the top level pom and all the modules at once, or
you can build them individually.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
