geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <>
Subject Re: [DISCUSS] specs versioning
Date Tue, 12 Dec 2006 01:45:47 GMT
I agree that parts of server should be split up into a few smaller  
chunks... but I can tell you from current experience with what we  
have so far, and from past experence where I worked on systems larger  
than G with each bit versioned separately... that the more versions  
you put in the mix, the more work and headache it is going to be to  
keep the system in order.

The less versions to manage the better... that does not mean only one  
version for everything, but a limited number of components that are  
managed and versioned together.  IMO specs are one of those  
components that should be managed and versioned together.

I do not think we want to end up with the same cluster* that maven  
exists in today with all of its components, some from ASF, some from  
Codehaus, all versioned up separately, can't easily tell which  
versions are compatible with each other, can't tell which is the  
latest.  I think following maven's practice would be a huge mistake.


On Dec 11, 2006, at 5:34 PM, Dain Sundstrom wrote:

> On Dec 11, 2006, at 1:55 PM, Jason Dillon wrote:
>> On Dec 11, 2006, at 12:16 PM, Dain Sundstrom wrote:
>>> In that case, why not move specs into the server tree?
>> Why not version each module in the server tree separately?
> Because many of the server modules are HIGHLY coupled which makes  
> releasing them independently very difficult.  For the modules that  
> are independently useful and not highly coupled, I think we should  
> version them independently (but not in "modules").
> -dain

View raw message