Sure, I gonna take a look on this one. Thanks!
Regards JB On Mon, Nov 9, 2026 at 5:54 PM Dominik Przybysz via dev < [email protected]> wrote: > Hi JBO, > could you take a look at the PR https://github.com/apache/aries/pull/951 > It drops the blueprint-api and use the artifact from org.osgi everywhere. > > Additionally, what do you think about the spring related artifacts? Should > we keep it? Also do we need *compatibility artifacts or we can drop them? > > pon., 9 lis 2026 o 13:26 Jean-Baptiste Onofré <[email protected]> > napisał(a): > > > Hi Dominik, > > > > +1 with the release plan. > > > > Thanks! > > > > Regards > > JB > > > > On Sat, Nov 7, 2026 at 11:08 PM Dominik Przybysz <[email protected]> > > wrote: > > > > > Hi, > > > today I ported JBO blueprint changes planned for java >= 17 ( > > > https://github.com/apache/aries/pull/923) to the current trunk and it > > > means > > > that we have blueprint artifacts that pass tests on all LTS versions - > 8, > > > 11, 17, 21 and 25. > > > > > > I would like then to propose the release of all the blueprint > artifacts: > > > > > > - blueprint-api - I would drop this artifact and replace all the usages > > > with > > > > > > > > > https://mvnrepository.com/artifact/org.osgi/org.osgi.service.blueprint/1.0.2 > > > > > > - blueprint-authz - 1.0.1 - dependencies updates > > > - blueprint-bundle - 1.3.0 - dependencies updates > > > - blueprint-cm - 1.3.3 - dependencies updates > > > - blueprint-compatibility - 1.0.1 (correlated with blueprint-bundle) - > or > > > drop as not necessary/not supported anymore > > > - blueprint-core - 1.10.4 - dependency updates > > > - blueprint-core-compatibility - 1.0.1 (correlated with > blueprint-core) - > > > or drop as not necessary/not supported anymore > > > - blueprint-jexl-evaluator - 1.1.1 - dependencies updates > > > - blueprint-noosgi - 1.2.1 - dependencies updates > > > - blueprint-parser - 1.6.2 - dependencies updates > > > - blueprint-repository - 1.5.0 - new blueprint artifacts and > dependencies > > > updates > > > - blueprint-spring - 0.7.0 - dependencies updates - or the question if > > > spring support is necessary here (never released version 1.x - > > > > > > > > > https://mvnrepository.com/artifact/org.apache.aries.blueprint/org.apache.aries.blueprint.spring > > > ) > > > - blueprint-spring-camel - 0.1.0 - dependencies updates - or the > question > > > if spring support is necessary here as there were no release before > > > - blueprint-spring-extender - 0.5.0 - dependencies updates - or the > > > question if spring support is necessary here (never released version > 1.x > > - > > > > > > > > > https://mvnrepository.com/artifact/org.apache.aries.blueprint/org.apache.aries.blueprint.spring.extender > > > ) > > > - blueprint-web - 1.1.2 - dependencies updates > > > - blueprint-web-osgi - 1.0.2 - dependencies updates > > > > > > Additionally I would handle the blueprint-maven-plugin artifact > releases: > > > > > > - blueprint-maven-plugin - 1.10.1 - dependencies updates > > > - blueprint-maven-plugin-annotation - 1.3.1 - refresh release based on > > java > > > 8 > > > - blueprint-maven-plugin-pax-cdi-handlers - 1.0.1 - dependencies > updates > > > - blueprint-maven-plugin-spi - 1.1.1 - refresh release based on java 8 > > > - blueprint-maven-plugin-spring-handlers - 1.0.1 - dependencies updates > > > > > > What I plan before the release: > > > - test blueprint-api replacement with org.osgi.service.blueprint > > > - removal of NOTICE and LICENCE files from the source code in module - > as > > > Apache parent pom provides maven-remote-resources-plugin > > > > > > Please share any feedback to the release plan > > > > > > -- > > > Pozdrawiam / Regards, > > > Dominik Przybysz > > > > > > > > -- > Regards, > Dominik Przybysz >
