Hi Brian, About the bundle, we will keep using the maven-bundle-plugin and we have to use more fine grain in the import/export package declaration and avoid using wildcard.
I will check the 2.0 actual branch and explain more on this thread :) Regards, François Papon [email protected] Le 06/01/2019 à 04:59, Brian Demers a écrit : > Yes yes yes!! > > I’d like to split the core module up a little more too possibly pulling the > permissions logic (not 100% sure if that would work). I played with it a > while back and ran into issues with the OSGI bundling. > > I’ve never been really happy with the “bundle” package type, mainly due to > lack of knowledge (I think). Can you describe what you are thinking about for > 2.0? Keep using the bundle plugin? Fix mixed package names in jars? > > -Brian > >> On Jan 5, 2019, at 2:18 PM, Francois Papon <[email protected]> >> wrote: >> >> Hi all, >> >> According to Git history, we can see a branch about the next major >> release 2.0.0 with big changes on api design :) >> >> This work was made 3 years ago and I would like to know if we can move >> forward on it and include other interesting changes like: >> >> * upgrade minimum JDK version to 8 >> * support JDK 9/10/11 >> * better OSGi support (unique package declaration per bundle, review >> maven-bundle-plugin declaration) >> * improve Apache Karaf support (upgrade to Karaf 4.2.2, review >> features.xml, add itests for Karaf) >> * upgrade dependencies and plugins version >> >> It would be interesting to move this branch on master and create a >> maintenance branch for 1.4.x after we had released the 1.4.0 (actually >> on 1.4.0-RC2 and their is 3 issues left to cut the release). >> >> Thoughts? >> >> -- >> François Papon >> [email protected] >>
