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
None singleton bundles support #56
Comments
Hey. I hit this problem today, and we really need this to be able to include 2 guava versions in the target. I work around this right now by manually adding the second version to the .target file right now, but this is not cool :| |
Since content like this should be quite common these days: Any updates here?
The workaround I use right now is to add two maven artifacts:
|
There's not much active development so generally the things that actually get done basically get done because whomever wants it does the actual work. I've tried to make it really easy to set up a development environment to contribute: I'll review pull requests and answer questions... |
It turns out that since #130 the editor validator accepts identical IU names having non-overlapping version ranges, but just one of them actually ends up in the generated .target file it seems. |
That seems trickier to fix. I don't know the implementation details very well. Are you continuing to investigate. I'm happy to help where I can. I have quite a bit of experience with p2 and PDE... |
Thanks! |
Regarding version overrides: - a specified version range always is fulfilled - within the same location declaration: - first declaration resolves to most recent as declared - subsequent unversioned declaration resolves to any former one - across subsequent location declarations: - earlier unversioned declaration is overridden - later unversioned declaration resolves to most recent available
Findings for today: |
Regarding overrides: - a specified version range always is resolved - within the same location declaration: - first declaration (with or without version) resolves - subsequent unversioned declaration is ignored - across subsequent location declarations: - earlier unversioned declaration is overridden - later unversioned declaration resolves to most recent available Regarding duplicates to be ignored: - within same location: has real 'duplicate' semantics - across locations: has 'redundant override' semantics
Regarding overrides: - a specified version range always is resolved - within the same location declaration: - first declaration (with or without version) resolves - subsequent unversioned declaration is ignored - across subsequent location declarations: - earlier unversioned declaration is overridden - later unversioned declaration resolves to most recent available Regarding duplicates to be ignored: - within same location: has real 'duplicate' semantics - across locations: has 'redundant override' semantics
Regarding overrides: - a specified version range always is resolved - within the same location declaration: - first declaration (with or without version) resolves - subsequent unversioned declaration is ignored - across subsequent location declarations: - earlier unversioned declaration is overridden - later unversioned declaration resolves to most recent available Regarding duplicates to be ignored: - within same location: has real 'duplicate' semantics - across locations: has 'redundant override' semantics
This is fixed and available in the latest nightly build: https://download.eclipse.org/cbi/updates/tpd/nightly/latest @haubi Thanks for your contribution! ❤️ 🥇 |
Currently none singletons processed as singletons in validation and .target generation. Example is .tpd file referencing three different versions of javax.wsdl from orbit repository. There are at least two problems in none singletons processing:
The text was updated successfully, but these errors were encountered: