Re: How to restrict access to sun.misc.Unsafe when using PaxExam ?

2017-11-23 Thread Christian Schneider
Do you maybe use boot delegation? Christian 2017-11-23 11:06 GMT+01:00 'Norman Maurer' via OPS4J : > Hmm I do not export it... Can I somehow see "who" export it ? > I only run the unit test and add my bundle to the config thats it. > > > Am Donnerstag, 23. November 2017 11:00:02 UTC+1 schrieb Ac

Re: How to restrict access to sun.misc.Unsafe when using PaxExam ?

2017-11-23 Thread 'Achim Nierbeck' via OPS4J
Hi, you could write a little test and do look for which bundle actually exports that package. for example with the following code you'll find all exports of all bundles ;) List bundleWirings = Arrays.stream(bundleContext.getBundles()) .map(bundle -> bundle.adapt(BundleWiring.class)).col

Re: How to restrict access to sun.misc.Unsafe when using PaxExam ?

2017-11-23 Thread 'Norman Maurer' via OPS4J
Hmm I do not export it... Can I somehow see "who" export it ? I only run the unit test and add my bundle to the config thats it. Am Donnerstag, 23. November 2017 11:00:02 UTC+1 schrieb Achim Nierbeck: > > Hi, > > first of all, if you don't have a bundle or system-fragment-bundle > exporting sun

Re: How to restrict access to sun.misc.Unsafe when using PaxExam ?

2017-11-23 Thread 'Achim Nierbeck' via OPS4J
Hi, first of all, if you don't have a bundle or system-fragment-bundle exporting sun.misc* it won't be available at all. As per default the framework itself only provides following packages (defined per spec): java.* As you can see here[1] some more are per default exported. But sun.misc isn't one

How to restrict access to sun.misc.Unsafe when using PaxExam ?

2017-11-23 Thread 'Norman Maurer' via OPS4J
Hi all, I am trying to use @RunWith(PaxExam.class) and restrict the access to sun.misc.Unsafe while doing this. I want to do this to write a unit that ensure we are still able to init a class when sun.misc.Unsafe is not present. Any idea how to do this ? So far I could not find any way to do so