Re: [HttpClient] to split or not to split

Hi Roland, I am also concerned about osgi entries and trying to look around how others have solved those issues... Up to this moment I gave a look at spring distro (http://springframework.cvs.sourceforge.net/springframework/spring/osgi/bnd/) and saw that they use a 'bnd' tool of Peter Kriens which

Re: [HttpClient] to split or not to split

Hi Sam, What we do for LimeWire is generate all our individual jars, then combine them using a quick ant task. (The jar task lets you provide other jars and will include their contents into the new one, or you can unzip the jars into a temporary directory and rejar them as a single jar.) I hav

Re: [HttpClient] to split or not to split

What we do for LimeWire is generate all our individual jars, then combine them using a quick ant task. (The jar task lets you provide other jars and will include their contents into the new one, or you can unzip the jars into a temporary directory and rejar them as a single jar.) I have absolutel

Re: [HttpClient] to split or not to split

Hi Stojce, > I think that would be better to have separate maven modules and 2 > options with distribution 1) separate 2) single-jar just as it's > handled in spring... The problem is that we don't know how to quickly modify the build process to generate a single JAR. cheers, Roland >_As Oleg

Re: [HttpClient] to split or not to split

I think that would be better to have separate maven modules and 2 options with distribution 1) separate 2) single-jar just as it's handled in spring... As Oleg noted 'core' part is mainly used for proxy servers and such, so those can use just 'conn' module for example... Cheers, Stojce __

Re: [HttpClient] to split or not to split

Hi Oleg, > I believe it is easier to drop the separate dependencies. OK, let's do it this way. cheers, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [HttpClient] to split or not to split

On Sun, 2008-02-17 at 19:19 +0100, Roland Weber wrote: > Hi Oleg, > > > No one seems interested. Let's bury this idea (well, until HttpClient 5 > > probably) > > Well, I for one am interested in having a maintainable code base. > I don't care _how_ we achieve this. If it means to drop the > sepa

Re: [HttpClient] to split or not to split

Hi Oleg, No one seems interested. Let's bury this idea (well, until HttpClient 5 probably) Well, I for one am interested in having a maintainable code base. I don't care _how_ we achieve this. If it means to drop the separate dependencies and for example allow usage of logging all over module-

Re: [HttpClient] to split or not to split

On Fri, 2008-02-01 at 19:41 +0100, Roland Weber wrote: > Hi folks, > > should we split module-client into multiple modules? > There are currently four informal units [1] there: > - HttpAuth > - HttpConn > - HttpCookie > - HttpClient > > Most of the arguments _for_ splitting module-client > are h

[HttpClient] to split or not to split

Hi folks, should we split module-client into multiple modules? There are currently four informal units [1] there: - HttpAuth - HttpConn - HttpCookie - HttpClient Most of the arguments _for_ splitting module-client are hypothetical. We are not going to put any modules on a separate release cycle i