Richard S. Hall wrote: > Actually, Commons is the perfect place for javax.servlet, it just didn't > exist at the time. > > However, we actually need version 2.1 of javax.servlet for the HTTP > Service, but I imagine that other people might want newer versions of > javax.servlet. Did we devise our approach for maintaining multiple > versions of bundles in Commons? It seems that would be necessary. We discusses this but did not come to a real conclusion. Now I think, the current approach is sufficient. Once a wrapper bundle is released it is very unlikely that there will be another release of this bundle with the same version as obviously the wrapped library does not change anymore. So a newer release is only required if there has been a buggy pom/bundle description.
Therefore I think its overkill to create a module per wrapped library and version, like a module for servlet-2.1, another one for servlet-2.2 etc. Once they are released they are not needed anymore. My idea was to release the latest versions of the wrapped bundles from commons with the exception of javax.servlet. There we could simply release a wrapped 2.1, 2.2, 2.3 and 2.4 one after the other. Its just a release 2.1, update the version in the pom, release 2.2 etc. Each release is tagged so if there is any need to rerelease a wrapped bundle we can create a branch from the tag. > > Other than that issue, I am all for moving javax.servlet to Commons. Great :) Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
