Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <45DF18EE.2060402@dubioso.net>
Date: Fri, 23 Feb 2007 17:40:14 +0100
From: Roland Weber <http-async@dubioso.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.0.9) Gecko/20070102 SeaMonkey/1.0.7
MIME-Version: 1.0
To: felix-dev@incubator.apache.org
Subject: Re: (FELIX-212) commons-httpclient 3.0.1 wrapping
References: <20015089.1172102946208.JavaMail.jira@brutus>
	 <45DDC945.8020801@dubioso.net>
 <568753d90702221203i3f3ec2banc09ff9d5fc5b28e8@mail.gmail.com>
In-Reply-To: <568753d90702221203i3f3ec2banc09ff9d5fc5b28e8@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Enrique,

> Thanks for the tip.  However, the bundling process simply repackages
> the library jar to include bundle metadata.  With the bundle metadata,
> the jar can now be added to an OSGi runtime, but no code is actively
> started.  Consumers of the bundle would need to be aware of the issue
> you mention.

thanks for the explanation. I thought that all bundles were required
to clean up after themselves. What tool do you use to generate the info
in the manifest? I can't promise anything, but if it is easy to integrate
into our Maven 1 build process and can be run with an old JVM
(HttpClient 3.x is still compatible with 1.2.2) we might add it to
HttpClient 3.1 RC1. I'll open an issue right away, but discussions will
have to wait for some weeks. The lead developer is going on a vacation
and I'll be on a business trip starting next week.

cheers,
  Roland