You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by thully <tm...@eng.ucsd.edu> on 2014/12/30 02:26:40 UTC
Bundles that depend on sun.* classes?
While our basic distribution of Cytoscape (built on Karaf) does not use any
classes in the sun.*/com.sun.* packages, we have been receiving questions
from third-party app developers regarding the use of such classes in app
bundles.
Currently, these developers are instructing their users to add these
packages to the org.osgi.framework.bootdelegation in custom.properties.
While that works, it is obviously unintuitive for users. Is there any harm
in customizing the distribution to include these packages in
custom.properties by default? Is there a better solution to this issue for
those who need these packages?
(I know that using sun packages is not advised - we don't do it and don't
want to encourage it, though it seems that in some cases it is hard to avoid
- particularly when a library is involved.)
--
View this message in context: http://karaf.922171.n3.nabble.com/Bundles-that-depend-on-sun-classes-tp4037465.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Bundles that depend on sun.* classes?
Posted by thully <tm...@eng.ucsd.edu>.
This is an application used by external users - as such, they could have any
JRE version that we support (currently that would include 1.7.x and 1.8.x).
In any case, what's the difference between putting it in boot delegation vs
the JRE entries?
--
View this message in context: http://karaf.922171.n3.nabble.com/Bundles-that-depend-on-sun-classes-tp4037465p4037523.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Bundles that depend on sun.* classes?
Posted by Kevin Carr <ks...@gmail.com>.
You only need to add them for the jre version you are using.
On Tue, Dec 30, 2014 at 3:32 PM, thully <tm...@eng.ucsd.edu> wrote:
> Is there any particular advantage/disadvantage to modifying
> etc/jre.properties as compared to modifying
> org.osgi.framework.bootdelegation in custom.properties? The latter seems
> simpler, as we would only be adding the packages once as opposed to adding
> them for each individual JVM.
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Bundles-that-depend-on-sun-classes-tp4037465p4037487.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Scott Carr
Re: Bundles that depend on sun.* classes?
Posted by thully <tm...@eng.ucsd.edu>.
Is there any particular advantage/disadvantage to modifying
etc/jre.properties as compared to modifying
org.osgi.framework.bootdelegation in custom.properties? The latter seems
simpler, as we would only be adding the packages once as opposed to adding
them for each individual JVM.
--
View this message in context: http://karaf.922171.n3.nabble.com/Bundles-that-depend-on-sun-classes-tp4037465p4037487.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Bundles that depend on sun.* classes?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
you can tune the etc/jre.properties to define the system package.
Regards
JB
On 12/30/2014 02:26 AM, thully wrote:
> While our basic distribution of Cytoscape (built on Karaf) does not use any
> classes in the sun.*/com.sun.* packages, we have been receiving questions
> from third-party app developers regarding the use of such classes in app
> bundles.
>
> Currently, these developers are instructing their users to add these
> packages to the org.osgi.framework.bootdelegation in custom.properties.
> While that works, it is obviously unintuitive for users. Is there any harm
> in customizing the distribution to include these packages in
> custom.properties by default? Is there a better solution to this issue for
> those who need these packages?
>
> (I know that using sun packages is not advised - we don't do it and don't
> want to encourage it, though it seems that in some cases it is hard to avoid
> - particularly when a library is involved.)
>
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Bundles-that-depend-on-sun-classes-tp4037465.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Bundles that depend on sun.* classes?
Posted by Kevin Carr <ks...@gmail.com>.
Certain packages that I use including bonecp use sun packages for their
dependencies. I have create a custom distro that includes these in the
jre.properties to make them available. This seems to work pretty well.
On Mon, Dec 29, 2014 at 7:26 PM, thully <tm...@eng.ucsd.edu> wrote:
> While our basic distribution of Cytoscape (built on Karaf) does not use any
> classes in the sun.*/com.sun.* packages, we have been receiving questions
> from third-party app developers regarding the use of such classes in app
> bundles.
>
> Currently, these developers are instructing their users to add these
> packages to the org.osgi.framework.bootdelegation in custom.properties.
> While that works, it is obviously unintuitive for users. Is there any harm
> in customizing the distribution to include these packages in
> custom.properties by default? Is there a better solution to this issue for
> those who need these packages?
>
> (I know that using sun packages is not advised - we don't do it and don't
> want to encourage it, though it seems that in some cases it is hard to
> avoid
> - particularly when a library is involved.)
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Bundles-that-depend-on-sun-classes-tp4037465.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Scott Carr