Irvin Naylor (Inactive) added a comment - 10/Feb/21 3:36 PM [~aloraine] - I see now. I was thinking about that as well, it seemed as if the pom.xml and the manifest file weren't on the same page regarding what versions are required. That might have been the reason why the app store allowed it since I noticed it also said that it was compatible with 9.1.x and 10, just like in the manifest. I'm currently testing in 9.1.8 to see what happens when the app runs (since before I just tested to see if it showed up in the actual download manager.) but I'll poke around and see what else I can find

Ann Loraine added a comment - 10/Feb/21 3:39 PM - edited Looks like we need to modify the pom.xml as with here: https://bnd.bndtools.org/chapters/170-versioning.html FAQ: Why does bnd use only major and minor version component in import - package headers? The micro is left out because it generates a lot of unnecessary releases, this is similar to the maven release process. If you connect everything 100%, you cannot move anything unless all its dependencies are moved at the same time. We actually tried in the OSGi build to use micro version changes for default methods in Java 8 but found that it just creates an enormous ripple through effect in the build. Not depending on the micro version is a lubricant that does not kill any bundle out there that depends on you. This should not be a problem because a micro version is a deployment issue since the semantic versioning should be used for APIs and a micro change is not visible in the API. That said, this is bnd so obviously you can override it. You can override the default version policy is: -provider-policy = ${range;[==,=+)} -consumer-policy = ${range;[==,+)} Just set ‘===’ instead of ‘==’ for the floor version in your pom.xml in the section and you should be ok. <configuration> <_provider-policy>${range;[===,=+)}</_provider-policy> <_consumer-policy>${range;[===,+)}</_consumer-policy> </configuration>

Ann Loraine added a comment - 10/Feb/21 3:50 PM It looks to me like we can use "configuration" tags above to force the maven bundle plugin to specify micro versions. I'm not sure it will work, but I'd like to give it a try, so I made a new ticket for it. Do you want to give it a try? attn: Irvin Naylor

Irvin Naylor (Inactive) added a comment - 10/Feb/21 4:00 PM [~aloraine] I see, that makes sense! And sure, I could give it a shot.

Ann Loraine added a comment - 10/Feb/21 4:03 PM - edited Before you get started, I need to make a LoraineLab fork of Noor's repository. Once I do that, you should "fork" from that fork, since Noor is no longer available for merging pull requests into her code. (She is now working at Amazon )