Giacomo Pati wrote: > > Should this distinction be on the groupId? > Isn't the groupId just saying that all stuff in it belongs to the same > project? >
I had a discussion a while ago with Brett Porter about this when i was converting excalibur. Outcome was that ideally a groupId points to the root package of that module's sources, but ofcourse practically this is not always viable. So it's not only an indication of which project a module belongs to, it can also express something about the submodule/project/logical grouping within the application. The maven guys haven't nailed down the exact semantics of the groupId yet and they are aware of this. So let's not worry about it too much for now, we can always change it later. Jorg
