Hi Chuck,
I realise that this is a response to an old message of yours but I have a
GitHub project that may be of interest to you that brings OSGi to JavaFx.
https://github.com/jtkb/osgifx
It aims to be simpler than Drombler and is agnostic to the OSGi implementation.
It is still a work in pro
Hi Kerry:
Thanks for the note. Old indeed. I don't remember anything I learned
from that project (though I did keep the modules). I did get it to work
by including the module somebody mentioned. It seems so easy, looking
at that module, I can't understand why Felix doesn't do the export fo
That's pretty easy to answer.
Felix by default exports all standard Java SE packages. JavaFX is not part
of Java SE, it is an extension that is only available on a subset of Java
implementations.
Neil
On 12 Dec 2017 2:56 pm, "Chuck Davis" wrote:
> Hi Kerry:
>
> Thanks for the note. Old indeed
Additionally, the JavaFX exports should now be available on java9 ootb
(assuming the modules are on the module path). As Neil correctly
points out, the reason they are not on older version is exactly that -
we don't know if they are there or not. With java9, we can detect that
(and we do starting
Karl, thanks for that information.
On 12/12/2017 08:31 AM, Karl Pauls wrote:
Additionally, the JavaFX exports should now be available on java9 ootb
(assuming the modules are on the module path). As Neil correctly
points out, the reason they are not on older version is exactly that -
we don't
Hi Chuck,
No problem, I wasn't aware of the issues you were having i.e. felix not
exporting the javafx packages by default. In Karaf they are exported by default
but obviously not everyone wants all the functionality provided by Karaf.
You've given me the idea to include some integration tests
Hi,
First of all I have asked this question already on StackOverflow so apologies
for 'duplicating' :
https://stackoverflow.com/questions/47738402/override-require-capability-in-maven-bundle-plugin
I short, the Maven bundle plugin is duplicating my 'Require-Capability' headers
I manually set
I’d be interested to know the exact capabilities/requirements you supply and
that are generated.
If these capabilities/requirements are from DS components you should be able to
turn off generation in a bnd.bnd file with
-dsannotations-options:nocapabilities,norequirements
I haven’t used the ma
David,
I quickly tried your suggested POM modification and still generates the headers
for me, though I remember the underscore technique to pass instructions direct
to bnd so will investigate further.
The headers that are generated are:
Export-Service =
com.javatechnics.jpa.dao.BookServiceDa
Kerry,
I looked at your project and since you are not using any DS components what I
suggested does not apply. I have no idea where the generated
capabilities/requirement headers are coming from.
In general I think it is worth expending considerable effort to straighten out
the capabilities/r
10 matches
Mail list logo
