geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Hogstrom <>
Subject Re: What do we do about fixable problems in M5?
Date Wed, 05 Oct 2005 12:30:52 GMT
I think that will work but users won't find Geronimo incredibly useful if they 
have to pull a whole new build to fix a single problem.  I discovered a similar 
problem in TranQL that the 1.1 SNAPSHOT doesn't generate the right SQL syntax 
for DB2 and had to tweak the Syntax Generator.  So the option going forward is 
for someone to pull TranQL 1.2-SNAPSHOT which wil most likely break their build 
too because of the serialization problem (probably not likely with my example 
but a high probability for other types of fixes).

Sachin had the right idea of highlighting the issues with serialVersionUIDs but 
that was part of a larger problem.  I'll open a feature JIRA that focuses on 
improved serviceability which would encompass these recurring issues and we'll 
look for someone to step up to the plate and put a strategy together.


- Matt

Geir Magnusson Jr. wrote:
> On Oct 4, 2005, at 11:24 PM, David Jencks wrote:
>> Stefan Schmidt has found our first configuration problem in M5,  
>> namely that the listener name in the ejb builder in  config.tomcat.xml 
>> points half to tomcat and half to jetty.  This is  easy to fix by hand 
>> (change JettyWebContainer to  TomcatWebContainer).  However I doubt we 
>> want to rerelease M5 to  fix this.  What do we want to do about issues 
>> like this?  One  possibility is to have an "errata" page clearly 
>> linked from the  download page.
> That's a great idea.
>>   There must be some other possibilities, any ideas?
> 1) Can we capture this as some kind of functional test to prevent  from 
> happening again?
> 2) how long would it take to fix on branch/m5 (and head) and do a M6  
> tag off of branch/m5 (if people don't find that too nauseating) and  
> release that?
> geir

View raw message