Target file resolve, How to force ignore artifacts from a specific site? #332
-
When i have this target file:
and also besides that also our own p2 repo with some 3rd party plugins that are not shipped by eclipse/orbit Then i now have a big problem because that aries.dynamic.bundle above has in the manifest imports like: org.objectweb.asm;version="[9.1,10)",org.objectweb.asm.commons;version="[9.1,10)",org.objectweb.asm.util;version="[9.1,10)" so it from 9.1 until 10. but if you go to: https://download.eclipse.org/releases/2021-09/202109151000/plugins/ you see that that update site also includes asm_9.2 which eclipse itself doesn't need or use: https://download.eclipse.org/eclipse/updates/4.21/R-4.21-202109060500/plugins/ But i think because of that import tycho or p2 resolvement does try to match 9.2 that it finds in https://download.eclipse.org/releases/2021-09/ So i now get this error: [ERROR] Internal error: java.lang.RuntimeException: org.osgi.framework.BundleException: Bundle sablo cannot be resolved:sablo [18] because i think it finds 2 of them.. But it shouldn;t do that, i haven't selected those plugins, only some other features from https://download.eclipse.org/releases/2021-09/ like EGit. How can i stil use the above urls and target file and force tycho/p2 to not use 9.2 for this but keep what the main Eclipse SDK just wants to use (9.1)? I dont think this is fully tycho because also if i do an "export" from the target file editor and i see what it generates in the above scenario it also has both of those jar versions. the only way that i can fix this at this moment is not to use:
but for all 3 features i import there use there own repo:
if i do that, then it seems to be working again, the above error doesn't happen. But that is a bit annoying that i now need to use 3 specific update sites instead of just 1 does a target file has an option to force exclude stuff? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 26 replies
-
You can configure exclusion filters, beside that Tycho 2.5.x has a possible fix for this kind of resolution errors. |
Beta Was this translation helpful? Give feedback.
-
Just a note on this: Aries behaves correct here and having version ranges on package imports is actually a good thing... |
Beta Was this translation helpful? Give feedback.
-
ok after a lot of testing i finally did see that 1 pom file was still on tycho 2.3 ... But i can't still use the target like that, because the product build that i do is just in my eyes not ok: all kinds of duplicates, no idea which one really comes up and does what.. if i use the target file that doesn't use the https://download.eclipse.org/releases/2021-09/ as a whole but takes the 3 things i get from there from there own sites, the generated product is nice no doubles anymore, (asm itself and tree) and even utils is now just 9.1 and not only 9.2 (i wonder how that would match up at runtime) |
Beta Was this translation helpful? Give feedback.
-
I have a feeling that smth included in your product in 2021-09 have a requirement [9.2.0,..) which forces p2 to put both. Please check what else in your product requires asm and what are the version ranges. |
Beta Was this translation helpful? Give feedback.
ok after a lot of testing i finally did see that 1 pom file was still on tycho 2.3 ...
And changing that fixed at least the build problem, so tycho wise it can handle this now.
But i can't still use the target like that, because the product build that i do is just in my eyes not ok:
all kinds of duplicates, no idea which one really comes up and does what..
if i use the target file that doesn't use the https://download.eclipse.org/releases/2021-09/ as a whole but takes the 3 things i get from there from there own sites, the generated product is nice
no doubles anymore, (asm itself and tree) and even utils is now just 9.1 and not only 9.2 (i wonder how that would match up at runtime)