-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect version in module-info #17
Comments
I don't see a way to tell moditect to set the module attribute module_version_index to anything specific. It appears to use the While this is annoying, I wonder what practical issues it has because there is no way to require a specific version of a Java module. |
Tycho has a new feature to automatically match the pom-version with the manifest version see: https://github.com/eclipse/tycho/blob/master/RELEASE_NOTES.md#enhanced-support-for-maven-ci-friendly-versions |
I don't know if this is really an issue or if this causes problems. I just noticed that inconsistency when looking into another issue and I was wondering why org.eclipse.osgi is a SNAPSHOT although I downloaded the release version. Probably more a user confusion issue rather than a technical one. |
fyi:
|
Now that we are moving to use BND to generate the module-info class, we have moved to striping off the qualifier from the module-info version (see #53). I'm going to close this issue because it was about the incorrect version being set with our usage of modetect. There is still some work that needs to be done to make sure the BND production of module-info is correct #27. |
When bundles are discarded during Equinox construction (before init is called) the framework will force a refresh on the discarded bundles this may trigger already resolved bundles to be re-resolved. During the constructor call we must prevent non-extension bundles that get refreshed from resolving until after the framework has been initialized. Fixes eclipse-equinox#17
I just noticed that the module-info of org.eclipse.osgi has the version 3.17.200-SNAPSHOT while the bundle itself has the version 3.17.200.v20220215-2237 in the MANIFEST.MF.
The text was updated successfully, but these errors were encountered: