[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13232 at 1/24/13 12:57 PM: -------------------------------------------------------------- [~rcernich] {quote}I know I'm late to the party and I didn't read the whole history of comments, but it seems like this would be more useful if the tp projects were versioned along with JBT. Obviously, you could add min/max as necessary. This would allow me to say something akin to: use the target platform that goes with JBT 4.0, e.g. (maven management key) org.jboss.tools:target-platform:target:unified-min:4.0 As a downstream consumer, I don't really care what version of the Eclipse platform the TP is tied to, since I will be targeting some version of JBT (e.g. 4.0, 4.1, 5.0, etc.). The current approach leaves me having to map a JBT version to a TP version (unnecessarily so, in my opinion).{quote} The approach you're suggesting doesn't scale because there is not a 1-1 mapping that would allow to bind a version of JBT to a (min/max) target platforms couple. We change TPs more often that we release milestone of JBT at the beginning of a release stream; and less than there are JBT milestones at the end of the stream. Also some TPs are used in different stream (eg for now, JBT 4.1.0.Alpha1 shares the same minimal TP as JBT 4.0.0), and it's pretty difficult to maintain this mapping from target-platforms. That's why TPs now follow their own versioning scheme and JBT parent is updated to select one of the available TPs. I understand that, as a downstream consumer, it's not the easiest to guess which TP is used for which JBT. For that, you'll have to either check the parent pom of the JBT version you're targetting, the TP version is written in it; or simply come to mailing-list/IRC/whatever and ask. was (Author: mickael_istria): [~rcernich] {quote}I know I'm late to the party and I didn't read the whole history of comments, but it seems like this would be more useful if the tp projects were versioned along with JBT. Obviously, you could add min/max as necessary. This would allow me to say something akin to: use the target platform that goes with JBT 4.0, e.g. (maven management key) org.jboss.tools:target-platform:target:unified-min:4.0 As a downstream consumer, I don't really care what version of the Eclipse platform the TP is tied to, since I will be targeting some version of JBT (e.g. 4.0, 4.1, 5.0, etc.). The current approach leaves me having to map a JBT version to a TP version (unnecessarily so, in my opinion).{quote} The approach you're suggesting doesn't scale because there is not a 1-1 mapping that would allow to bind a version of JBT to a (min/max) target platforms couple. We change TPs more often that we release milestone of JBT at the beginning of a release stream; and less than there are JBT milestones at the end of the stream. Also some TPs are used in different stream (eg for now, JBT 4.1.0.Alpha1 shares the same minimal TP as JBT 4.0.0), and it's pretty difficult to maintain this mapping from target-platforms. That's why TPs now follow there versioning scheme and JBT parent is updated to select on of the available TPs. I understand that, as a downstream consumer, it's not the easiest why to guess which TP is used for JBT x. For that, you'll have to either check the parent pom of the JBT version you're targetting, the TP version is written in it; or simply come to mailing-list/IRC/whatever and ask. -- 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