geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <>
Subject Re: Drop the m1 build
Date Fri, 18 Aug 2006 04:23:22 GMT
I'm all for getting rid of those test related errors that are not  
errors (or maybe are errors and they test is broken and does not  
fail)... but I think they are independent.


On Aug 17, 2006, at 9:19 PM, Joe Bohn wrote:

> Does pristine mean that all those ugly runtime exceptions, gbean  
> start errors, illegal state errors, assertion errors, and  
> NoClassDefFound errors mentioned in the "Maven2 ... we are almost  
> there" thread will be resolved?   If so, and we must first remove  
> the m1 build to get these addressed, then I'm all for removal.
> I realize that many of those errors may be present with the M1  
> build (but just not logged as DJ pointed out) but seeing them now  
> makes the build look much worse than with M1.  I'm not sure what  
> level of confidence people have with the build when seeing these  
> all scroll by. It sure doesn't give me any warm fuzzies.
> Joe
> Jason Dillon wrote:
>> On Aug 17, 2006, at 8:18 PM, Bruce Snyder wrote:
>>> I caution against removing the m1 until the m2 build has been stable
>>> for a period of time. We made this mistake with ActiveMQ and
>>> ServiceMix and wound up having to restore the m1 build while  
>>> gremlins
>>> were flushed from the m2 build.
>> Hrm... its stable now :-P  And I am not really sure how well the  
>> m1  build works.
>>> I tend to think Jason's proposal is better one. Give it some time to
>>> be tested and get stable.
>> JVZ?
>> The m2 build has been in various stages of stablish for a few  
>> weeks now.
>> The main issue I have with keeping it around, and praying it  
>> still  works kinda... is that it prevents us from continuing to  
>> clean things  up (getting files into better places to reduce pom  
>> config, renaming  directories to conform to artifactIds, fixing  
>> variables used for  filtering).
>> There is still a week or so that needs to be spent post-removal of  
>> m1  to get the m2 build pristine... and I don't see any reason why  
>> we  should wait much longer before doing it.
>> --jason

View raw message