On Sun, 2006-06-18 at 13:03 -0700, Michael Becke wrote: > I forget the history here, but I'm thinking everything should probably > just be components under Jakarta HttpComponents. HttpCore has a > separate project, but perhaps it should just become a component under > HttpClient and then HttpClient should just be HttpComponents. > > Mike >
Mike, Both HttpCore and HttpAsync are being developed within the HttpComponents project along with other components and I see no reason for changing that. The trouble is that Jira requires a separate "project" per a versioned artifact. Therefore there is no way around creating a new project in Jira for HttpAsync if we want to be able to release separately from other components. It is still open for discussion whether HttpAsync should have its own release cycle or whether it should be released along with HttpClient. Does that make sense? Oleg > On 6/18/06, Roland Weber <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > the HttpAsync component has no home in JIRA yet. I've assigned previous > > issues to HttpClient 4.0, but I think we should introduce at least a > > separate component, if not project. Since the future role of HttpAsync > > within HttpComponents is yet unclear, I have no preference for either. > > > > What do you think? > > > > cheers, > > Roland > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
