I spent a lot of hours with genesis 1.x looking through all the poms
for the setting that was causing behavior I was wondering about to
want to eliminate every bit of unnecessary complexity I could.
In the event we come up with a flava that doesn't want to inherit
from default-flava we can put it as a direct child of the root
genesis project.
Fair enough :-)
I also changed the groupId to o.a.g.genesis from
o.a.g.genesis.flava.
why?
Fewer groupIds == simpler && better IMO. I don't see what the
additional groupId adds except complexity and chance for confusion.
Am I missing something?
Its just a tool for organizing similar modules, like packages in
java. I tend to organize stuff, which is why I put all flava's into
their own groupId.
--jason
