Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336499

Summary:	Indigo M5 Discovery UI installs Helios MDT/OCL Examples
Product:	[Modeling] Amalgam	Reporter:	Adolfo Sanchez-Barbudo Herrera <adolfosbh>
Component:	UI	Assignee:	Project Inbox <amalgam.ui-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	ed
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Adolfo Sanchez-Barbudo Herrera

2011-02-07 07:55:56 EST

Cedric,

While doing some testing using Modeling EPP I tried to install MDT/OCL Examples (Tools) using the Modeling UI Discovery. However, the version of the feature which UI discovery try to install corresponds to helios version.

After figuring out how MDT/OCL contributes to the Modeling UI Discovery, I downloaded the modeling.xmi file and I checked that the OCL Tools component set the following URL for its site:

http://download.eclipse.org/releases/indigo/

On the one hand:
a) We (MDT/OCL project) don't have any Indigo release.

On the other hand:
b) I'm wondering why discovery is trying to install Helios MDT/OCL Examples, if we are using the global ( http://download.eclipse.org/releases/indigo/)

Finally, I'm wondering what should we do until Indigo final release to test this functionality:
1. Do nothing, in the Indigo final release all will be in place (no testing at all :\ )
2. Do some magic with our P2 repositories so that when having an http://download.eclipse.org/releases/indigo/ in our installable component from the modeling.xmi file, a proper Indigo's repository is used (for instance, milestones one). I'd have to understand why b) above is occurring.
3. Trying to make this work adding a project-specific Indigo's repository in the Sites URL property in our installable component from the modeling.xmi file

In principle, 3 looks more sensible to me. If you agree I'll provide a patch, otherwise let me know what to do. In any case, an explanation of how UI Discovery is working will be very welcome ;)

Best Regards,
Adolfo.

Comment 1 Cedric Brun

2011-05-09 05:21:54 EDT

Hi Adolfo, 

Sorry for the lag, I'm taking up with the amalgam bugs right now.

We had an issue for M5 with an old amalgam build (from Helios) which was taken by the aggregation. 

please have a try with the M7 build, we have different discovery descriptor and it should take the indigo one now.

As for a), are you planning to have an Indigo release or not ? Is that all of MDT OCL or just the "OCL Examples"?  as OCL itself is already in the package I can easily remove the discovery entry for the OCL examples if you want.  Looking at the staging site I see that OCL examples and Editors is built,I guess that was an M5 issue.

Comment 2 Adolfo Sanchez-Barbudo Herrera

2011-05-09 07:40:48 EDT

Cedric,

All looks in place.  This morning I made the OCL Examples installation through the Modeling UI Discovery, so it's working as expected. So yes, it looks like an old issue which has been fixed.

Cheers,
Adolfo.

Comment 3 Cedric Brun

2011-05-09 08:44:25 EDT

Thanks for your feedback

Comment 4 Ed Willink

2011-05-09 12:12:06 EDT

(In reply to comment #2)
> All looks in place.  This morning I made the OCL Examples installation through
> the Modeling UI Discovery, so it's working as expected. So yes, it looks like
> an old issue which has been fixed.

OCL Examples is correct in M7 EPP, but Xtext and Acceleo are not; they install M6 not M7.

Comment 5 Ed Willink

2011-05-27 14:49:55 EDT

(In reply to comment #4)
Just did an RC2 EPP install even though the Modeling EPP is not on the public page.

Everything seemed sensible; not even a sign of Xtext/Orbit conflict.