You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Consider OSGi artifacts using apache felix maven plugin #39
Well, I love the new upcoming energy and interest for this project. I'm still following what you're doing. But it's now like 3 or 4 years ago that I needed jssc and worked with OSGi. It was a project talking to some Zigbee modems. But I'm not working on the project anymore... Still I'm trying to help though :)
-What it is:
OSGi (only a really rough overview, just in my own words, no resp. in correctness or completness): https://www.osgi.org/ is a framework which allows code to be organized in modules. These modules can be loaded / unloaded dynamically during runtime (you get lifecycle management). Think of it like android apps. The main advantage is improved stability of systems and easy manageability.
-if we need it:
tough question as jssc is a very "low level" library, I would suggest to just "support it".
-How to implement and test it:
If I remember correctly, it's now like 4 years ago, there was only a file missing, which indicates to osgi what this library contains and needs. It is just a descriptor.xml, which get's generated by maven during the build, hence my earlier work.
So I would suggest implementing a build system like maven or gradle and I think it will take responsibility for most of it. Also I'm now more experienced in maven and I can take a look at my old pom.xml.
Maybe I can reactivate my old osgi environment and create a test environment. For testing, I can maybe provide an example for a test setup and document it in the wiki; or you could set up something like jenkins, travis or so.
Hey @vogt31337 thanks for showing up! That sounds great! Your diff is still available, and I did a lot of work on the maven part. Maybe you already peeked at the other issues?
If you like, join us on slack. We have native developers and java developers. And I think we already made good progress. :-)
BTW: Maven is already implemented. Not finished yet, but enough for a quick intermediate release.
After that, I was planning additional repositories for parent-pom, natives and maybe natives-header. See #40
Activity
vogt31337 commentedon Apr 14, 2019
Well, I love the new upcoming energy and interest for this project. I'm still following what you're doing. But it's now like 3 or 4 years ago that I needed jssc and worked with OSGi. It was a project talking to some Zigbee modems. But I'm not working on the project anymore... Still I'm trying to help though :)
-What it is:
OSGi (only a really rough overview, just in my own words, no resp. in correctness or completness): https://www.osgi.org/ is a framework which allows code to be organized in modules. These modules can be loaded / unloaded dynamically during runtime (you get lifecycle management). Think of it like android apps. The main advantage is improved stability of systems and easy manageability.
-if we need it:
tough question as jssc is a very "low level" library, I would suggest to just "support it".
-How to implement and test it:
If I remember correctly, it's now like 4 years ago, there was only a file missing, which indicates to osgi what this library contains and needs. It is just a descriptor.xml, which get's generated by maven during the build, hence my earlier work.
So I would suggest implementing a build system like maven or gradle and I think it will take responsibility for most of it. Also I'm now more experienced in maven and I can take a look at my old pom.xml.
Maybe I can reactivate my old osgi environment and create a test environment. For testing, I can maybe provide an example for a test setup and document it in the wiki; or you could set up something like jenkins, travis or so.
bmarwell commentedon Apr 14, 2019
Hey @vogt31337 thanks for showing up! That sounds great! Your diff is still available, and I did a lot of work on the maven part. Maybe you already peeked at the other issues?
If you like, join us on slack. We have native developers and java developers. And I think we already made good progress. :-)
BTW: Maven is already implemented. Not finished yet, but enough for a quick intermediate release.
After that, I was planning additional repositories for parent-pom, natives and maybe natives-header. See #40
Load the native library from jssc's own class loader (java-native#39)
Extract a new copy when the boot path library is bound to another cla…
Read jssc.boot.library.path from OSGi framework properties (java-nati…
Add OSGi bundle metadata to jar manifest (java-native#39)
Load the native library from jssc's own class loader (java-native#39)
Extract a new copy when the boot path library is bound to another cla…
Read jssc.boot.library.path from OSGi framework properties (java-nati…
Add OSGi bundle metadata to jar manifest (java-native#39)
Load the native library from jssc's own class loader (java-native#39)
Extract a new copy when the boot path library is bound to another cla…
Read jssc.boot.library.path from OSGi framework properties (java-nati…