[
https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi...
]
Rob Cernich commented on JBIDE-13232:
-------------------------------------
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).
Just my two cents.
refactor target platforms' GAVs, names, labels (was target
platforms has the same name)
---------------------------------------------------------------------------------------
Key: JBIDE-13232
URL:
https://issues.jboss.org/browse/JBIDE-13232
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Environment:
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha1
Attachments: JBIDE13232.parent.pom.tweaks.txt
.target files are all called "e42-wtp34-jbds6" even though they are for
jbosstools and not specific to jbds6 either.
Makes it hard to actually see which target platform to choose
--
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