[
https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2505:
----------------------------------
Eclipse rules state that just because a plugin is x.y.z+1, does not mean that its
containing feature must also be x.y.z+1. The feature, if nothing in its ACTUAL CONTENT
(eg., feature.xml, LICENSE.html, etc.) has changed, can remain at x.y.z. No commits == no
upversioning, even if a contained plugin has a commit for maintenance and its version
increments.
http://wiki.eclipse.org/Version_Numbering#Versioning_features
Of course in JBT/JBDS, we upversion both feature AND plugin at the same time, as we follow
a different convention.
JBDS 6.0.1 is based on Juno SR0 instead of SR2
----------------------------------------------
Key: JBDS-2505
URL:
https://issues.jboss.org/browse/JBDS-2505
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build
Affects Versions: 6.0.1.GA
Environment: JBDS 6.0.1.CR1a B354
Reporter: Martin Malina
Assignee: Nick Boldt
Priority: Blocker
Labels: respin-b
Fix For: 6.0.1.GA
JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect
something 4.22.1 (still Juno SR2). But in fact it is SR0.
My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse,
the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse
Juno 4.2.1.
--
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