Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <47B87A99.8090108@dubioso.net>
Date: Sun, 17 Feb 2008 19:19:05 +0100
From: Roland Weber <ossfwot@dubioso.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.12) Gecko/20080210 SeaMonkey/1.1.8
MIME-Version: 1.0
To: HttpComponents Project <dev@hc.apache.org>
Subject: Re: [HttpClient] to split or not to split
References: <47A367DC.1060501@dubioso.net> <1203102726.5746.10.camel@ubuntu>
In-Reply-To: <1203102726.5746.10.camel@ubuntu>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

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-client, that's fine with me. If it means that we
properly document the sub-modules and set up a nightly build
process that compiles the different parts separately with the
correct dependencies only, that's fine with me too. If somebody
comes up with a way to teach Maven this trick, just the better.
I may even go so far as to only modify my local Ant built to
use separate compilation units with specific dependencies.

But the current situation is that we have different dependencies
for different parts of a single compilation module, without
automatic checks by any build process anywhere and even without a
proper documentation. I refuse to carry on with this beyond alpha3.

cheers,
   Roland


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org