| Summary: | Add GMF Tooling to Indigo Modeling package | ||
|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Mickael Istria <mistria> |
| Component: | modeling-package | Assignee: | Project Inbox <epp.packager-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, cedric.brun |
| Version: | unspecified | ||
| Target Milestone: | 1.3.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Mickael Istria
Hi Mickael, We've been working a lot last year on streamlining the package and only keeping a minimum platform + providing a discovery mechanism so that end-users can easily extend the package. We did define a set of rules to get included in the platform package: [http://wiki.eclipse.org/ModelingAmalgam], two of those are not looking ok to me speaking about GMF Tooling : 1- a low UI profile 2- small (including non-packaged dependencies) We want to avoid a big package including everything in Modeling which would make it un-usable and think it's better to ease the discovery and installation of the modeling projects. Even doing so we have one of the biggest packages already. That said GMF Tooling is an important component from a community perspective and I'd be very pleased to highlight this in some way in the package, any idea to get there ? Closing the bug, if you've got any other idea to hightlight the GMF tooling in the package or in the discovery feel free to re-open. GMF-Tooling is currently living a difficult transition so that we could even not get it part of Indigo, then I agree with you for not getting it part of the package or the discovery now... However, it there a way to become part of the discovery later, without waiting for next year release train ? Let's wait for the results of your poll to show that people who use Modeling Package want an SDK, and then it should be enough to prove that GMF-Tooling is relevant in it ;) |