Hi Christian,
Thanks for the point me to the mailing list. I was not subscribed
>.<.
About the Eclipse installation. The problem is that I'm using the
update manager to install IMP and there is a strict dependency with a
Eclipse 3.4 feature which doesn't allow me to install the tool.
"Cannot complete the request. See the details.
Cannot find a solution satisfying the following requirements
org.eclipse.jdt.feature.jar
[3.4.0.v20080603-2000-7o7tEAXEFpPqqoXxgaBhhhq]"
Once installed (in a Ganymede installation), I'll have to use the tool
to generate code which will effectively have Eclipse 3.5 as the target
platform. However I firstly have to play a little bit with the tool to
see how it works. Afterwards, I'll have to try to generate code
suitable for Eclipse 3.5. Besides, IMP uses lpg v2 while OCL uses lpg
v1.1. Therefore, I clearly have to distinguish different platforms to
use, at development-time and at run-time.
I wish I didn't find any problem with this ;P.
Thanks for the help...
Cheers,
Adolfo.
Christian W. Damus escribió:
Hi, Adolfo,
This is a good question for the OCL dev mailing list, so I copy
my reply there. I am assuming that you are subscribed to that list ...
:-)
The org.eclipse.ocl.ecore plug-in requires Ecore 2.5 because it
extends the Ecore metamodel. This is a rather tight coupling with a
dependency that can change in ways that are incompatible with
subclasses, not to mention that the practice of extending Ecore is
explicitly not supported by the EMF project. So, this is akin to using
the internal API of a dependency and necessitates keeping in locked
step with the dependency's version.
Can you use IMP in an Eclipse 3.4 workbench that has an Eclipse
3.5 PDE Target?
Cheers,
Christian
On 2-Dec-08, at 9:29 AM, Adolfo Sánchez-Barbudo Herrera wrote:
Hi Christian,
A little doubt about the plugin versions.
I have noticed that ocl.ecore plugin has a dependency on emf 2.5
plugin. However if I download the version to 2.4 in the dependency all
seems to work well.
I suppose that the whole OCL SDK must depend on EMF 2.5 because of UML
3.0.0. But I'm not sure if the own ocl.ecore plugin must have that
dependency on EMF 2.5. I suppose that it is a good policy keeping a
(not too) old plugin version dependency, so that clients don't have to
work with the last-in-develop component id they don't really need it.
However I'm not sure about that.
Do you have any advice about this ?
I need to use Eclipse 3.4 while trying IMP tool (I can't use Eclipse
3.5), and I don't want to download Eclipse 3.5, EMF 2.5, etc, into my
workspace If I don't really need it. And because of I only need version
1.3 of ocl.ecore (and ocl) plugin, it would be nice for me if it
depended on EMF 2.4. But I'm not sure if this is a good policy...
Thanks in advance for the help.
Cheers,
Adolfo.
--
<logo.jpg>
|
Adolfo
Sánchez-Barbudo Herrera
adolfosbh@xxxxxxxxxxxxxxxx
C/Elías Ramos González, 4, ofc. 304
38001 SANTA CRUZ DE TENERIFE
Tel.: +34 922 240231 / +34 617 718268 |
--
|
Adolfo
Sánchez-Barbudo Herrera
adolfosbh@xxxxxxxxxxxxxxxx
C/Elías Ramos González, 4, ofc. 304
38001 SANTA CRUZ DE TENERIFE
Tel.: +34 922 240231 / +34 617 718268 |
|
