Closed steinarb closed 6 years ago
Right...! Code using OSGi support won't build with vaadin version <8.1.0 and so will fail with the vaadin 8.0.0 of TouchKit 8.4.1. I will have to make the pull request based on the vaadin version upgrade
On the other hand: if the fix to #9 is done first, then the travis-ci build will run fine when this change is pulled in, and this pull request will merge without conflicts with the pull fixing #9.
So I'll just let this pull request be.
Awesome, looks good to me!
BTW. Could vaadin-osgi-integration dependency be optional or provided?
I merged this right away to see the build result. We can see what to do with the osgi-integration dependency still.
Great that you've merged it in! Thanks! :-)
The OSGi support should not interfere with with touchkit usage as a regular jar, so I don't think there is any need to make it optional.
The support consists of:
Oops! The pull request also contained this one: 364cfe8
I pushed it to the OSGi branch after making the pull request and wasn't aware that the pull request would contain anything I pushed to the branch.
What the commit does is to embed a font from the "base" theme used by the TouchKit widgetset. Without this change the arrows are lacking from NativeSelect dropdown and in NavigationView navigation links, when running in OSGi.
But I don't know what the effect would be for two different jars containing the same resource in a non-OSGi setting?
I'm also not sure if there are copyright considerations by embedding the font in touchkit?
False alarm: the embedding of the font from base, is in the pull request now, but wasn't at the time the pull request was merged, and therefore isn't on master.
This part of github pull request behaviour was a bit confusing.
Adds OSGi support to TouchKit 5.0.1-SNAPSHOT, the changes are: