Comments (10)
Thanks for reporting. This is definitely a bug. However you should be able to work around it by adding a "proxy" bundle to your workspace, which has no content, just the two "Require-Bundle"s for the two versions, and add that in the launch configuration instead.
from lcdsl.
Thanks for the hint. However, I only need this to work around issues in the auto-resolving, not my own plugins. Thus, I don't want to maintain additional artifacts.
Specifically:
- Xtext needs org.antlr.runtime 3.2, Sirius needs 4.3
- E4 needs org.apache.batik.css 1.6, several others 1.10
from lcdsl.
Understood. Whilst I do want to fix this bug of course, you can still work around the issues with a single bundle with dependencies to all the doubled-up-dependencies. Nobody needs to actually use that bundle, it is just there to tear in additional dependencies that are impossible to declare with this bug.
(I know, you need to maintain that in your sources, and thats not nice. But OTOH, you would need to maintain this list of dependencies in the launch config otherwise...)
from lcdsl.
Yes, the real issue is the auto-resolver who does not understand this constraint and adds only the newest version (for both regular and LcDsl launch configs, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=472778).
from lcdsl.
Well, we do have dependencies to multiple guava versions transitively in our application, and LcDsl is able to generate launch configuration which contain both versions. We do NOT use the same resolver as Eclipse itself. I actually proposed a patch for the resolver a while ago. AFAIK the most current Eclipse has a different fix for the issue.
see https://bugs.eclipse.org/bugs/show_bug.cgi?id=489319
Re-reading the upstream bug: do you have simpleconfigurator checked in your launch configuration?
from lcdsl.
What is simpleconfigurator? Maybe I looked up the wrong bug.
Your remark on resolver might explain another issue I have: My launch config behaves differently whether I run it via the menu bar or via the launch configs dialog. I didn't report it yet because my project is not yet available for you to look into (will change soon; it's a newer version of https://github.com/altran-mde/xtext-sirius-integration).
from lcdsl.
Simpleconfigurator is a simple implementation of a OSGi framework configurator which defines which bundles should be loaded by the runtime. It uses a bundles.info file which is generated if simpleconfigurator is used. Unfortunately it seems that Eclipse still defaults to using the ULTRA-legacy UpdateManager instead of P2 (the current mechanism for bundle management in RCP applications) which was used in very old Eclipse versions and does not /really/ know OSGi that well - especially duplicate bundles with just version difference don't work with it, even if the bundles are checked in the launch configuration.
from lcdsl.
Where do I choose the simpleconfigurator? I checked the launch config dialog and the preferences, and didn't find any hint.
from lcdsl.
Simply add the org.eclipse.equinox.simpleconfigurator (or so, from the top of my head) bundle to your launch configuration, or as dependency of your software.
from lcdsl.
doesn't really help; after clicking on "add required plugins" (in a regular launch config):
from lcdsl.
Related Issues (20)
- Eclipse "hangs" when using ${project_loc} in "content-provider" HOT 3
- How to launch Plug-in Tests? HOT 16
- new feature: Link to products / features / plugins HOT 3
- Provide default ID for launch config
- new feature: Add required dependencies HOT 3
- Working Sets HOT 1
- Easy access to raw launch configuration file HOT 1
- Missing ignored plugins should not generate a warning
- Updating the Xtext Community Website HOT 3
- NPE with unknown launch types HOT 5
- Missing latest version of org.eclipse.debug.ui.launchview HOT 2
- Startlevels for workspacebundles HOT 6
- Test class not accepting all JUnit5 variants HOT 1
- Support launch type pure JUnit? HOT 1
- Application `[No Application] - Headless Mode` unsupported. - Should be default
- regression: CI build hangs at "loading target platform" HOT 3
- Validation for test class is too strict
- Compile error due to using API 11, but 1.8 on classpath HOT 1
- Introduction of variables in lcdsl
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lcdsl.