eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

[releng] Features missing in download packages / Galileo update site #469

Closed eclipse-ocl-bot closed 1 month ago

eclipse-ocl-bot commented 1 month ago

| --- | --- | | Bugzilla Link | 296261 | | Status | CLOSED WORKSFORME | | Importance | P3 normal | | Reported | Nov 26, 2009 11:54 EDT | | Modified | May 27, 2011 02:48 EDT | | Reporter | Christian K. |

Description

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)\ Build Identifier: 1.2.3 and 1.3.0

I want to reference an OCL SDK as a dependency in my feature, to enforce that the SDK is installed when my feature is installed with the update manager. Additionally the referenced feature needs to be present in my target platform so that the reference can be resolved during development.\ Now I have two candidates for the reference, either org.eclipse.ocl.all.sdk or org.eclipse.emf.ocl.sdk. Now the problem is that I can use neither of those two since:

  1. org.eclipse.emf.ocl.sdk is not included in the official Galileo update site. I verified this by looking at http://download.eclipse.org/releases/galileo/aggregate/artifacts.jar
  2. org.eclipse.ocl.all.sdk is not included in the mdt-ocl-SDK-*.zip downloads which I'm using to setup my target platform.

The org.eclipse.ocl.all.sdk feature is only included in the mdt-ocl-Update-*.zip files but I would want to avoid to use these instead since the layout is different and I'm using a script to setup my target platform which also consumes a bunch of other SDK Zip files.

I may workaround this somehow by referencing the elements of the SDK features directly but I'm stimm supecting an incosistency here. To my understnading the Galileo update site should at least contain the org.eclipse.emf.ocl.sdk feature.

Reproducible: Always

eclipse-ocl-bot commented 1 month ago

By Alexander Igdalov on Dec 02, 2009 09:27

Christian,

We are not planning to fix this for the Galileo release. In Helios we get rid of the org.eclipse.emf.ocl.sdk feature. The only recommended way to install OCL is to use the update site since other installation approaches may fail due to the changes in the Eclipse plugin installation policy.

Perhaps, you might find the comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=289595#c9 useful.

HTH,

eclipse-ocl-bot commented 1 month ago

By Christian K. on Dec 02, 2009 10:47

That's fine with me, I found a workaround to my issue. I'm now referencing the individual features contained in org.eclipse.emf.ocl.sdk/org.eclipse.ocl.all.sdk. Not so convenient but it works.

Just as a suggestions: Maybe you can make sure that with the Helios release an OCL feature is available that contains runtime, sources and docs. That is avaiable both in the SDK ZIP download and the offcial Helios update site.\ This will make things easier for us since we are consuming OCL in several different scenarios.

eclipse-ocl-bot commented 1 month ago

By Ed Willink on May 27, 2011 02:48

Closing after over 18 months in resolved state.