[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] JmDNS ExecutionEnvironment bump to Java 5
- From: Wim Jongman <wim.jongman@xxxxxxxxx>
- Date: Wed, 29 Sep 2010 18:38:38 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=JQFCtQ1iAI2NquTqnEv1HXT/JC8PDsf6kfIv+4wt9KkNmLY/dPdxIZox05HVjrD+xd u0nPbyG/Pn0RAbMAMbQSvho5OuwF9XwHVVY50x4ugPGI+9AD1Kj8HIqPpAH5r5IBeuXS XAOQ3nuyKEsAXUAgRcSCUsKrBXpTriQyJ4HEM=
Does this also work for @overrride on interface methods (1.6 > 1.5)?
On Wed, Sep 29, 2010 at 6:06 PM, Scott Lewis <slewis@xxxxxxxxxxxxx>
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.