[
https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2505:
----------------------------------
Having a plugin increment and a feature NOT is SOP* for
Eclipse.org. Since the contents of
the feature have not changed, there's no need to upversion it. That said, to ensure
the new plugin can be installed on top of an old one the hash suffix on the feature
version is incremented so that it will be seen as new.
Thus you might have org.foo.feature_4.2.1.datestamp-hashabc and a month later, when
org.foo plugin 4.2.2 is released, the feature will be rebuilt as
org.foo.feature_4.2.1.datestamp-hashabf, using the same datestamp but a newer hash (abc
< abf).
* - SOP = Standard Operating Procedures
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