aem-global-parent 1.15.12 makes building of content packages with sling:OsgiConfig fail

i assume it's fixed with filevault-package-maven-plugin 1.3.0

you can give it a try with io.wcm.maven.aem-global-parent 2.0.7-SNAPSHOT

yes, will update as soon as it gets available.

@Stefan The ticket is resolved. I guess we now need to wait until it will be released.

Yes, I agree. But since we do a lot of implementations, we have projects that still use them. I would assume that there are more projects that use aem-global-parent and also still use sling:OsgiConfig.

The project I’m working on has a few, so I think I will migrate them. But another project I’m on has 300+ sling:OsgiConfig nodes, which is a lot more cumbersome.

btw. using “sling:OsgiConfig” nodes is very outdated and should no longer be used. best practices for the last years was using .config files instead (using felix config admin syntax), and this best practice was recently replaced with a new OSGi standard using .cfg.json files (see example)

i’ve never tested the latest filevault package maven plugin with sling:OsgiConfig nodes for years as we’ve got rid of them for a long time.

let’s see what turns out.