[ https://issues.jboss.org/browse/JBTIS-66?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBTIS-66: --------------------------------- Reason for this respun version of 0.2.5 is best summed up by these comments from [~bbrodt]: {quote} Well folks, up until now I was under the assumption that I was building the bpmn2 editor with the latest version of graphiti 0.10.0-M6 - I did not realize that the MANIFEST.MF bundle-version="[0.8.2,0.10.0] does NOT include M6 (whodathunkit?) So this bpmn2 editor migration to the version of graphiti that will ship with kepler is going to take longer than I thought. This API change affects about 20 or so classes and there ain't no going back. This means I'll have to maintain 3 different code bases for helios, indigo/juno, and kepler. The best, short-term solution is that we continue to use graphiti 0.9.2 for both juno and kepler builds until kepler releases in June. That will give me time to work on a new branch for graphiti 0.10.x. ---- I'm going to change the bpmn2 editor manifest files to require [0.8.2,0.11.0] but the project pom will still have this repo definition for kepler builds: <repository> <id>eclipse-graphiti-kepler</id> <url>http://download.eclipse.org/graphiti/updates/milestones/S-0.10.0M6... <layout>p2</layout> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>true</enabled> </releases> </repository> and update this as graphiti & kepler get to their release dates. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira