sounds good to me. I will work this once Mike lets me know that he has everything checked in.
On 8/22/07, Trustin Lee <[EMAIL PROTECTED]> wrote: > > On 8/22/07, Mike Heath <[EMAIL PROTECTED]> wrote: > > Mark wrote: > > > Just so we are straight on terminology, what I referred to as a MINA > > > component is what I think you all are calling sub-projects. I will be > sure > > > to get this right from now on. These include: > > > > > > mina-example > > > mina-filter-codec-netty > > > mina-filter-compression > > > mina-integration-jmx > > > mina-integration-spring > > > > > > I would say that these are optional components of MINA since they are > > part of the MINA build and all share the same version. When we do a > > MINA release we vote on, build, and distribute all of these modules and > > not just mina-core. I don't think async-httpclient should be tied to > > this process. > > > > I think a better home for async-httpclient would be to create something > > like https://svn.apache.org/repos/asf/mina/async-httpclient and put > > 'trunk', 'tags', and 'branches' in there. Then in trunk put a parent > > pom.xml that builds the 'client' and 'examples' modules. This would > > make async-httpclient totally independent of the MINA release cycle. > > > > Do others see things differently? > > We might be able to extract common codec from both server and client > side into a separate module and let two depend on it, resulting three > submodules in total: > > * mina-filter-codec-http > * mina-protocol-server-http > * mina-protocol-client-http > > wdty? > > Trustin > -- > what we call human nature is actually human habit > -- > http://gleamynode.net/ > -- > PGP Key ID: 0x0255ECA6 > -- ..Cheers Mark
