Torsten Curdt wrote:
> First thought: Why "modules"? Everyone talks about
> "multi-projects" and "artifacts"
I try to avoid calling it multiproject for this reason.
So how do you call it then? ;)
multi-module
> When I tried to build the (main) project I got told off that packaging
> was meant to be "pom" not "jar" ...ok - but why?
Currently, there's no real concept of aggregation in the standard
packaging plugins, so it makes no sense to have a build root with a type
other than pom.
I meant: why shouldn't also the parent pom have a src directory and
generate a jar? I don't understand the concept of this distinction
that forces me to have all my code in modules.
It would be counter-intuitive unless it were aggregating.
Next big thing would be aggregation support for the surefire plugin.
Does anyone have that on his cards yet?
Not that I know of.
- Brett
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
