Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <508E386C.5030108@nanthrax.net>
Date: Mon, 29 Oct 2012 09:03:56 +0100
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: Fwd: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for
 Java 7
References: <20cf3010e66155771904ccfb03ce@google.com>
 <A6D0C785-7D0B-4587-8FD3-E92CA25070F6@adobe.com>
In-Reply-To: <A6D0C785-7D0B-4587-8FD3-E92CA25070F6@adobe.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

FYI,

the 4.3.1 artifacts have not yet been deployed on Central.

Regards
JB

On 10/29/2012 09:00 AM, Felix Meschberger wrote:
> FYI in case you missed it.
>
> In short: The OSGi R 4.3 libraries have been recompiled with Java 5 tar=
get and republished as version 4.3.1 to maven. So to use OSGi R 4.3 libra=
ries in a Java 5 (and up) environment you should use the 4.3.1 version de=
pendency.
>
> Nothing to be done when using older (4.2.0 and before) dependencies bec=
ause they are compiled for Java 1.4.
>
> Regards
> Felix
>
> Anfang der weitergeleiteten E-Mail:
>
> Von: BJ Hargrave <bj@bjhargrave.com<mailto:bj@bjhargrave.com>>
> Betreff: [osgi-blog] [OSGi Alliance Blog] 4.3 Companion Code for Java 7
> Datum: 26. Oktober 2012 21:06:11 MESZ
> An: "osgi-blog@mail.osgi.org<mailto:osgi-blog@mail.osgi.org>" <osgi-blo=
g@mail.osgi.org<mailto:osgi-blog@mail.osgi.org>>
> Antwort an: Private list for OSGi blog discussion <osgi-blog@mail.osgi.=
org<mailto:osgi-blog@mail.osgi.org>>
>
> Starting in version 4.3, OSGi started to use generics in some of the AP=
I including the Core specification. Generics were introduced<https://en.w=
ikipedia.org/wiki/Generics_in_Java> to the Java language in Java 5. Howev=
er, OSGi needed to continue to support embedded use cases which use the C=
DC/Foundation 1.1 runtime which is still based upon the Java 1.4 language=
 level and JVM. To address this issue, OSGi compiled the APIs with -targe=
t jsr14<http://www.ibm.com/developerworks/java/library/j-jtp02277/index.h=
tml>; an undocumented javac flag introduced before Java 5 was final. So w=
e had the best of both worlds: we can use generics and still compile to r=
un on Java 1.4 based runtimes.
>
> This worked for Java 5 and Java 6. But when Java 7 shipped, two things =
changed: javac no longer understood the jsr14 option to -target and javac=
 refused to recognize the attributes containing the generics information =
in class files already compiled with -target jsr14. The change to no long=
er support creating -target jsr14 class files was ok; we could continue t=
o compile with Java 6 javac. But the change to the javac to cease to reco=
gnize the class file attributes with the generics information in existing=
 class files was a bigger problem. It meant that the 4.3 API jars publish=
ed by OSGi were not useable by people who need to compile with Java 7 jav=
ac. By not useable, I mean javac treated the classes as if they did not c=
ontain any generics information: they were raw. A bug<http://bugs.sun.com=
/bugdatabase/view_bug.do?bug_id=3D7078419> was filed against Java to see =
if this was some mistake or oversight. The reply was that the change was =
intentional.
>
> At the time this was first noticed<https://mail.osgi.org/pipermail/osgi=
-dev/2011-August/003223.html>, Java 7 was new and not too widely used. OS=
Gi also included the source code in the jars so you could recompile the c=
ode yourself if you needed. Later, when it came time to ship Core R5, we =
changed to compile the API classes with -target 1.5 and so they work fine=
 on Java 7. So problem solved; the new release's jars don't use -target j=
sr14! Except some of the current OSGi implementations (I'm looking at you=
 Felix<https://felix.apache.org/> and Karaf<https://karaf.apache.org/>) a=
re still based upon Core 4.3 and thus people using those implementations =
still need to use the Core 4.3 API. And if they also want to use Java 7, =
they need to recompile the OSGi API source. So after some prodding by a f=
ew folks, OSGi rebuilt the Core and Compendium API jars as Core 4.3.1<htt=
p://www.osgi.org/Download/File?url=3D/download/r4v43/osgi.core-4.3.1.jar>=
 and Compendium 4.3.1<http://www.osgi.org/Download/F
ile?url=3D/download/r4v43/osgi.cmpn-4.3.1.jar>. The new jars have the sam=
e packages at the same package versions having the same API signatures. T=
hey are just not compiled with -target jsr14 so they work fine with Java =
7.
>
> So if you need to use the 4.3 API with Java 7, pick up these new 4.3.1 =
jars. They should also be available on maven<http://mvnrepository.com/art=
ifact/org.osgi> shortly.
>
> --
> Posted By BJ Hargrave to OSGi Alliance Blog<http://blog.osgi.org/2012/1=
0/43-companion-code-for-java-7.html> at 10/26/2012 07:06:00 PM __________=
_____________________________________
> osgi-blog mailing list
> osgi-blog@mail.osgi.org<mailto:osgi-blog@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-blog
>
>

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com