[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] JmDNS ExecutionEnvironment bump to Java 5
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Thu, 30 Sep 2010 09:34:47 -0700
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20100915 Thunderbird/3.1.4
On 9/30/2010 9:15 AM, Markus Alexander Kuppe wrote:
On 09/29/2010 06:13 PM, Markus Alexander Kuppe wrote:
On 09/29/2010 06:06 PM, Scott Lewis wrote:
Are we compiling the JmDNS from source? If so, we could set the source
level to 1.5, but have the compile output (javacTarget) be to 1.4 (as we
are doing with a couple of other bundles...e.g.
org.eclipse.ecf.remoteservice). Then we could keep the bree at 1.4.
This will work for generics...but we do need to be careful that no
1.5-specific jre API calls are made in the jmdns code.
And that is exactly the case. JmDNS 3.2 uses the new concurrent API
present in Java5.
I've backported JmDNS to Java 1.4. That made an new dependency towards
the concurrency backport bundle from Oribit (edu.emory.mathcs.backport)
necessary and a couple of code changes (edu.emory.mathcs.backport does
not support generics).
Although I think it's great to be able to support 1.4 as bree in
general, I'm not sure it's worth the additional code (size) in the Emory
backport + the build/releng/distribution/support complexity of including
the Emory codebase...given that we haven't heard from anyone that
requires 1.4 support for jmdns...on this list anyway. And of course the
backport could be invalidated by additional/other changes to jmdns.
But I guess since you've already done the hard work of the backport I
suppose we might as well use it.