Hi, Before we proceed with the agreed new directory structure, we need to decide what groupId and artifactId each components should have. It's pretty evident for existing mina-* artifact (except for HTTP stuff), but It's somewhat unclear for ftp and http directory.
1) Should all three's groupId be 'org.apache.mina', or should the two have different groupIds like 'org.apache.mina.http' and 'org.apache.mina.ftp'? I have no particular preference here. 2) What should be the new artifactId of mina-filter-codec-http and mina-protocol-http-client? I think Jeff and other AsyncWeb contributors could give me some idea. I prefer to keep mina-filter-codec-http unchanged and to change mina-protocol-http-client to something like 'ahc' or something like faster-than-light. Any better idea is appreciated. Trustin On Jan 22, 2008 6:37 AM, Niklas Gustavsson <[EMAIL PROTECTED]> wrote: > > peter royal wrote: > >> i propose something different.. > >> > >> /mina/(trunk|tags|branches) - core, examples, transports, statematchine > >> > >> /http/(trunk|tags|branches) - filter-codec-http, protocol-http-client, > >> asyncweb > >> > >> /ftp/(trunk|tags|branches) - ftpserver (and a separate codec if its > >> desired to fragment it some > > > This one makes perfect sense to me. +1. I would not like having parts of > FtpServer in two different versioning (trunk/tags) structures. > > /niklas > > -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
