Installing a new version of Groovy on my OSGi environment makes my bundle import it, though it shouldn’t

Don’t use a version range. Explicitly set the version of groovy.util
This might not seem helpful, but I believe it will work. We get a very similar problem when we try to generate Karaf features.xml files on dependencies with version ranges (we worked around this by writing our own plugin that removed the upper versioned item from the finished features file 🙁 )

Leave a Comment