I may be about to suggest something that is impossible or that would have loads of negative side effects that with my limited knowledge I'm not aware of...
Having read this wish from @aeric, and having spotted the same thing in the B4XTable library manifest a few days ago I wondered if it would be possible for developers to use wildcards when declaring dependencies in the manifest file?
Taking the B4XTable as an example, the manifest would contain something like sqlite-jdbc-*.jar or sqlite-jdbc-3.*.jar rather than specifically sqlite-jdbc-3.7.2.jar.
When compiling, the IDE would then pick up whichever version of the sqlite-jdbc jar is in the developers libraries folder or any 3.x.x version in the case of the second wildcard example above
Having read this wish from @aeric, and having spotted the same thing in the B4XTable library manifest a few days ago I wondered if it would be possible for developers to use wildcards when declaring dependencies in the manifest file?
Taking the B4XTable as an example, the manifest would contain something like sqlite-jdbc-*.jar or sqlite-jdbc-3.*.jar rather than specifically sqlite-jdbc-3.7.2.jar.
When compiling, the IDE would then pick up whichever version of the sqlite-jdbc jar is in the developers libraries folder or any 3.x.x version in the case of the second wildcard example above
Last edited:
