I gave the justification several times. You are choosing to disregard it. Java API is not bundle’s sole API. I don’t consider a restriction in requirements a compatible change. DTP 2 is certainly not a drop-in replacement for DTP 1.12 and the version numbering truthfully communicates that fact.
I understand the temptation to fudge the truth when it comes to version numbers, but that doesn’t make it a sound engineering practice. - Konstantin From: Ed Willink Sent: Wednesday, October 28, 2015 6:29 AM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] DTP major version bump for Neon On 28/10/2015 13:13, Konstantin Komissarchik wrote: I have no specific plans re ODA’s Java API. So absolutely no justification for a change then. There is no need for all plugins to bump together. It is cosmetically nice to see all plugins with the same version, but it just isn't tenable long term. For instance many OCL plugins remain at 3.x although those that have been affected by UML major changes have moved to 4.x and 5.x. Inflicting a major change on clients is not a bit of a pain, it is a major pain, particularly for those clients that are stable and consequently have minimal maintenance teams. In some cases useful but unmaintained tools, such as UML2 Tools, are killed by the major version change. Regards Ed Willink
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
