We hardcoded the JCR 1.0 dependency years ago to be sure to support JCR
1.0 regardless of the dependencies. That's probably a legacy artifact
now and letting bnd do the work seems much better
Having a dependency for just a single simple method seems a little bit
odd to me, especially as our co
Also supporting JCR 1.0 via
https://github.com/apache/sling-org-apache-sling-installer-provider-jcr/blob/914ef527268860dd85082ad0c2afe86cd284b1b6/pom.xml#L68
seems weird to me and I would like to get rid of that and let bnd determine
import ranges automatically.
WDYT?
> On 5. Jan 2020, at 13:16
Hi and happy new year to everyone,
I am currently bringing the OSGi installer to the newest parent and therefore
reviewing the dependencies.
In
https://github.com/apache/sling-org-apache-sling-installer-provider-jcr/blob/914ef527268860dd85082ad0c2afe86cd284b1b6/src/main/java/org/apache/sling/inst
