On Mar 20, 2007, at 6:00 AM, David Jencks wrote:
I don't think we've been specific enough about what goes where for jason's proposal to make sense yet, as gianni points out.

I'm sure we don't want all 100K artifacts we produce all under o.a.g or o.a.g.server

I was assuming that o.a.g.server would basically have the kernel and system stuff in it and little else -- maybe some basic naming support.

then e.g. o.a.g.connector would have connector, transaction, jpa, connector-builder, persistence builder in it with the appropriate configs as well

Folks, don't get a head of yourselves... there are a few different issues here.

One of them is the groupId for that we have now with the structure we have now. I believe that we should change the base groupId to org.apache.geroniom.server to match to svn module. This can be done now, or soon, and should probably be done at the same time when the plugins groupId is changed.

Everything else is related to large scale restructuring of the project, the above has nothing to do with restructuring. I have sent email about this before, though we've never come to any conclusions about how to resolve it. And... right now I don't think we need to come to any conclusions, as I don't think we are ready to start on this work yet.


That way no group would be too large to understand at once. However I think it might still be good to have some easy way to distinguish the code subprojects from the car/module subprojects and I'm not sure how to do that well yet. Right now there are 2 indications: whether the artifact ends up in modules or configs, and whether it starts with "geronimo-" or ends with .car.

Sure, we need to solve this problem. I'm not sure what the best solution is, though for the g1.1-amq4 stuff I simply suffixed the car modules with "-config":

     https://svn.apache.org/repos/asf/geronimo/sandbox/g1.1-activemq4/

I hope we can eventually get the server/trunk tree organized so that features, like amq, can be organized into directories like this one, where all (or most) of the modules are all peers like this.

--jason

Reply via email to