search

rzel / concurrentlinkedhashmap

Automatically exported from code.google.com/p/concurrentlinkedhashmap
Apache License 2.0
0 stars 0 forks source link

Make ConcurrentLinkedHashMap available as an OSGi bundle #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please consider to make ConcurrentLinkedHashMap available as an OSGi bundle. 
Any other libraries (or applications) which depend on ConcurrentLinkedHashMap 
and which are already available or are soon planned to become available as OSGi 
bundles will benefit from this.

Complexity / Amount of Change Required:

Should be relatively small. The packaging in the pom.xml file needs to change 
from jar to bundle and the maven-bundle-plugin needs to be configured. See the 
Guava's pom.xml for an example.

Original issue reported on code.google.com by simeon.malchev on 6 Apr 2014 at 1:12

GoogleCodeExporter commented 9 years ago 
I just realized that ConcurrentLinkedHashMap is actually available as an OSGi 
bundle in Maven Central. Apparently the ConcurrentLinkedHashMap bundle is 
created using Bnd-1.50.0 tool. Please close this issue.

Original comment by simeon.malchev on 22 Apr 2014 at 1:09

GoogleCodeExporter commented 9 years ago 
For Apache Karaf 2.3.3 it is enough to change the maven-bundle-plugin 
configuration and add:
            <Import-Package>                
                !sun.misc.*,
                *
            </Import-Package>

Original comment by gabriel....@apogado.com on 12 May 2014 at 1:53

GoogleCodeExporter commented 9 years ago 
Is there any reason to be importing the sun.misc APIs? Its means that this jar 
will likely only work on Oracle JVMs. AIX and HP-UX environments.

Original comment by colm.br...@gmail.com on 28 May 2014 at 7:57

GoogleCodeExporter commented 9 years ago 
After digging Ive noted that the entire impl relys on the Unsafe class. I think 
this answers my question.

Original comment by colm.br...@gmail.com on 28 May 2014 at 9:25

GoogleCodeExporter commented 9 years ago 
I'm sorry for not being available to resolve this issue. I'm sure by now you've 
worked around it using org.osgi.framework.system.packages.extr property. I'd 
like to fix and release v1.4.1 so that workaround isn't necessary.

It appears that the common solution is to add,
<Import-Package>sun.misc.*resolution:=optional</Import-Package>

Should I use that configuration or the one you provided? (Sorry, I'm not 
familiar with OSGi).

Original comment by Ben.Manes@gmail.com on 15 Dec 2014 at 8:02

GoogleCodeExporter commented 9 years ago 
Issue 42 has been merged into this issue.

Original comment by Ben.Manes@gmail.com on 15 Dec 2014 at 8:04

GoogleCodeExporter commented 9 years ago 
Released v1.4.1 with an optional import rule.

Original comment by Ben.Manes@gmail.com on 17 Dec 2014 at 2:55