| Summary: | Make Graphiti part of the Indigo repository | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Michael Wenz <michael.wenz> | ||||
| Component: | Core | Assignee: | Project Inbox <graphiti-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P2 | Flags: | michael.wenz:
indigo+
|
||||
| Version: | 0.8.0 | ||||||
| Target Milestone: | 0.8.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | Indigo M4 theme_release_train | ||||||
| Attachments: |
|
||||||
|
Description
Michael Wenz
Additional things that need to be done: - Do a test run for the M3 milestone (update site, aggregation build, etc.) - Switch Graphiti build to consume Indigo milestones - Find out what is necessary to become part of the Model Amalgamation and do it Assured that the central build at hudson.eclipse.org builds against Indigo milestones. Graphiti's offset category will be +3, entered on http://wiki.eclipse.org/Indigo/Participating_Projects#Offset_category Most of our dependencies have offset 0 (eclipse core) or +1 (emf, gef), but emf.transaction and emf.workspace have +2 Created attachment 183915 [details]
Patch for the Indigo aggregation
Attached as patch because local test build before check-in did not yet get through and I don't want to risk loosing the change during my vacation
I checked-in the changes to org.eeclipse.indigo.build (callisto repository) to add Graphiti to the Indigo release train update site (see Indigo aggregation patch). Preparation work for participating in release train is finished. Follow-up actions: Globalisation: https://bugs.eclipse.org/bugs/show_bug.cgi?id=323359 Usage of non-APIs: https://bugs.eclipse.org/bugs/show_bug.cgi?id=327669 Further complete requirements from this page (not tracked here): http://eclipse.org/indigo/planning/SimultaneousReleaseOverview.php?action=project&projectid=modeling.gmp.graphiti Graphiti is part of Indigo M4 Part of Graphiti Indigo 0.8.0 |