| Summary: | Add Xpand middleend and backend to the Helios update site | ||
|---|---|---|---|
| Product: | [Modeling] M2T | Reporter: | André Arnold <andre.arnold> |
| Component: | Xpand | Assignee: | Project Inbox <m2t.xpand-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | dennis.huebner, pelder.eclipse |
| Version: | 1.0.0 | Flags: | andre.arnold:
helios+
|
| Target Milestone: | SR1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
André Arnold
(In reply to comment #0) > The following features of M2T Xpand should become available on the Helios > update site: > > org.eclipse.xtend.backend.sdk (1.0.0) > org.eclipse.xtend.middleend.xpand.sdk (1.0.0) > > The features are currently only available on the M2T Xpand update site > beginning with the helios release. Adding new features to Helios is not a big deal, just adding two new entries in the m2t-xpand.build file. But I don't think that it will be approved by pmc's. There for, I propose SR1 as the target milestone. I do not see this as a problem. As I understand it, the purpose of the Helios site is to allow discovery of features by end users. In past releases we have been encouraged to provide a limited number of features published to the simultaneous release. Take a look at how many features EMF Core publishes to Helios (one) versus how many are published on the modeling aggregation site (too many to count). To me, it seems unlikely that any end user would want to install only the back-end and middle-end features. Listing them in the Helios site would only result in confusion and clutter. (In reply to comment #0) > The following features of M2T Xpand should become available on the Helios > update site: > > org.eclipse.xtend.backend.sdk (1.0.0) > org.eclipse.xtend.middleend.xpand.sdk (1.0.0) > > The features are currently only available on the M2T Xpand update site > beginning with the helios release. André, Backend & Co. is now availble under http://www.eclipse.org/modeling/updates/ (modeling aggregation site). Regards, Dennis. (In reply to comment #2) > I do not see this as a problem. As I understand it, the purpose of the Helios > site is to allow discovery of features by end users. In past releases we have > been encouraged to provide a limited number of features published to the > simultaneous release. Take a look at how many features EMF Core publishes to > Helios (one) versus how many are published on the modeling aggregation site > (too many to count). > > To me, it seems unlikely that any end user would want to install only the > back-end and middle-end features. Listing them in the Helios site would only > result in confusion and clutter. Paul's point seems reasonable to me. Hence, I think we can close this bug. Maybe, adding the Xpand Middleend and Backend to the Xpand SDK would be a better solution. |