Kaloyan,
No, a client that has compiled against your current version remains
binary compatible with your new version. No need to recompile or change
their code. They just can't run anymore unless they satisfy the highest
BREE of all their requirements. The version increment should reflect
changes in the APIs and implementations. I think a BREE change just
implies a content change which implies a micro version increment.
Cheers,
Ed
On 24/10/2015 11:55 AM, Kaloyan Raev wrote:
Hi,
Does moving to Java 8 justify the bump of the major version? Many
projects update their BREE without updating their major version.
Greetings,
Kaloyan
On Fri, Oct 23, 2015 at 12:37 PM, Konstantin Komissarchik
<[email protected]
<mailto:[email protected]>> wrote:
DTP will soon contribute v2 to Neon aggregation stream. The
current version is 1.12.1. The reason for the major version bump
is the move to requiring Java 8. All DTP plugins and features
will get a major version bump.
I recommend all consuming projects to prepare for this ahead of
time by relaxing the version ranges.
Thanks,
- Konstantin
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
<mailto:[email protected]>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
