I fixed the one for org.eclipse.jst.j2ee.ejb
The version number was increased in CVS, but the
change was not released.
Greetings,
Kaloyan
There are
just a few cases where service fields still need to be
incremented for our 3.2.3 release (compared to 3.2.2).
I'd appreciate these being
fixed early in the week, just to make sure there is no
ripple effects, such as in comparator tests.
There are these "known" cases,
below, but also use care when releasing any of the last few
fixes this week that the versioning is correct for bundles
and features effected.
Note, I think it's fair to
release fixes for versioning without "PMC Reviewed Bug"
since it is pretty much a "must have" and as long as you
release only an increase in service field, perfectly safe.
Please do open a bug if its more than that.
Thanks
= = = = = = =
Bundles with
qualifier-only increases
org.eclipse.jpt.core
2.3.2.v201102022310 (current)
2.3.2.v201008252310 (reference)
org.eclipse.jpt.eclipselink.core
1.3.1.v201102022310 (current)
1.3.1.v201007142310 (reference)
org.eclipse.jst.j2ee.ejb
1.1.401.v201101310842 (current)
1.1.401.v201007150400 (reference)
Features with
qualifier-only increases
org.eclipse.jpt.eclipselink.feature
2.3.2.v201008242310-7778BjBgJ9EA9VGYDFBA (current)
2.3.2.v201008242310-7778BjBgJ9E99_H_DFBA (reference)
org.eclipse.jpt.eclipselink_sdk.feature
2.3.2.v201008242310-55384CACEmMlQEKECXQhNQPwChKA (current)
2.3.2.v201008242310-55384CACEmMlQEKDCbRjNQPwChKA
(reference)
org.eclipse.jst.enterprise_core.feature
3.2.1.v201007070821-52FMTAkF7B87ODN7_DA (current)
3.2.1.v201007070821-52FMTAkF7B77UBR7W98 (reference)