On maven modules

[alessio...@gmail.com]

Hi there,
Luca recently tried adding a module to TestedBy for his maven plugin
sources. While doing that, he basically made the project change from a
single module project to a multi-module project. This means the parent
pom.xml needed to be declared with "pom" packaging type as it needed
to be the parent of all modules' pom.xml files. One of the side
effects of this move (which btw made Luca revert his commit for now)
was that the tests declared in the parent were not run anymore.
Now, the point is we either need to have a real multi-module project -
meaning the code written till now has to be moved to a "core" module
or something like that- or the new maven plugin has to stay as a
standalone project, declaring dependency on the actual TestedBy
artifact (and TestedBy stays as single module project).
The latter option would imply different lifecyles for main project and
plugins, which might even make sense. WDYT?

[Stefano Maestri]

I vote for 2 different projects. The main reason for me is that they can have different lifecycle.

bye
S.

[Alessio Soldano]

Fine to me (my implicit vote was already for opt 2), btw single module
also implies easier management ;-)
Cheers
Alessio

Stefano Maestri wrote:
> I vote for 2 different projects. The main reason for me is that they
> can have different lifecycle.
>
> bye
> S.
>
> On Fri, Oct 9, 2009 at 11:35 PM, alessio...@gmail.com

> <mailto:alessio...@gmail.com> <alessio...@gmail.com