| Unable to run a Sirius-based product from Eclipse Luna [message #1610256] |
Tue, 10 February 2015 12:22  |
Eclipse User |
|
|
|
Hello,
I am studying the possibility to embed Sirius editors in a packaged RCP-based application, but I have not been very successful so far. I have been trying to study existing applications packaged as Eclipse products (Arduino Designer, Dart Designer and UML-Designer), but when I launch the product after having retrieved the latest source from GitHub, the application never starts due to dependency problems, such as:
Unresolved requirement: Import-Package: com.google.common.collect
Unresolved requirement: Require-Bundle: com.google.guava
Unresolved requirement: Require-Bundle: org.eclipse.ocl
Unresolved requirement: Import-Package: com.google.common.base; version="11.0.2,16.0.0)"
Unresolved requirement: Require-Bundle: org.eclipse.emf.edit.ui; bundle-version="[2.3.0,3.0.0)"; visibility:="reexport"
Unresolved requirement: Require-Bundle: org.apache.batik.util; bundle-version="[1.6.0,1.7.0)"
but the corresponding dependencies are part of my Eclipse installation (based on Eclipse EMT Luna - I tried with Sirius 1.0.2 and 2.0.2).
Does it mean there is some extra packaging task to perform before trying to run the product ? Are these products compatible with recent Sirius or Eclipse releases ?
By chance, is there anywhere on GitHub a "dummy" Sirius-based Eclipse product working out of the box with Eclipse Luna and Sirius 1 or 2 ?
Thanks in advance.
[Updated on: Wed, 11 February 2015 10:33] by Moderator |
|
|
| Re: Unable to run a Sirius-based product from Eclipse Luna [message #1682818 is a reply to message #1610256] |
Tue, 17 March 2015 18:04  |
| Eclipse User |
|
|
|
I had a similar problem.
The problem here is that you *already* are importing some of those packages, but a more recent version. For example, for org.apache.batik.util I needed both 1.7.0 and 1.6.0. (In your log it states it needs 1.6.0 up to 1.7.0, but *excluding* 1.7.0, and you're probably importing 1.7.0)
Unfortuantely I haven't found a way to fix this permanently, but here's a workaround:
Run your product from the .product file, it won't run, but a new run configuration will be created
Edit your run configuration, in the plugins tab, adding the required versions
It should run now
You need to do this everytime you change your .product file
Unfortunately I think Sirius documentation is kinda basic, expecially on RCP.
[Updated on: Tue, 17 March 2015 18:17] by Moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.03721 seconds
Home