[
https://issues.jboss.org/browse/JBDS-1987?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1987 at 7/4/12 11:22 AM:
-----------------------------------------------------------
How about we adopt this approach?
2012: JBT 3.3 / JBDS 5.0 / Eclipse 3.7
2013: JBT 3.6 / JBDS 6.0 / Eclipse 4.2
2014: JBT 3.7 / JBDS 7.0 / Eclipse 4.3
In this scenario, the minor digit of JBT == major digit of JBDS = sum of major + minor
digits of the Eclipse version.
Also, the component with the largest version (Hibernate Tools 3.6) will match the overall
version (JBoss Tools 3.6), for an extra level of synchronicity.
was (Author: nickboldt):
How about we adopt this approach?
2012: JBT 3.3 / JBDS 5.0 / Eclipse 3.7
2013: JBT 3.6 / JBDS 6.0 / Eclipse 4.2
2014: JBT 3.7 / JBDS 7.0 / Eclipse 4.3
In this scenario, the minor digit of JBT == major digit of JBDS = sum of major + minor
digits of the Eclipse version.
Align JBDS and JBossTools version numbers for 6.0 release
---------------------------------------------------------
Key: JBDS-1987
URL:
https://issues.jboss.org/browse/JBDS-1987
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Build
Reporter: mark yarborough
Fix For: 6.x
Consider aligning version numbers between community and product bits.
Example (new):
JBDS 6.x derived from JBIDE 6.x
Rether than (old):
JBDS 6.x derived from JBIDE 4.x
See Product Management for more details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira