Re: [cross-project-issues-dev] Heads-up: core.expressions has increased to 3.5.0
On 05/01/2015 02:08 PM, Markus Keller wrote: To those who had a wrong version range like [3.4, 3.5): Please find the bug in your process that introduced this too-narrow dependency in the first place. If a tool generated that dependency, then please file a bug for that tool. https://wiki.eclipse.org/Version_Numbering#How_to_specify_plug-in_requirements This statement is correct wrt rules theory. From practical experience I'd like to add that the problem runs deeper: I've developed tools that got broken even by micro updates from other Eclipse projects. I read Markus' statement as a reminder that for Eclipse SDK bundles, upper bounds of major+1 *should* be the right thing to do, agreed. Unfortunately, this doesn't appear to be good advice for all of the release train. We could start a discussion about stricter enforcement of semantic versioning on the release train (incl. an update of what exactly is compatible API evolution wrt various technologies). Or we can accept the current state of affairs as reality. This would imply that letting any tool generate dependencies is insufficient - it requires human judgment to decide which range is appropriate for which dependency. Or maybe both. cheers, Stephan ___ 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
Re: [cross-project-issues-dev] Heads-up: core.expressions has increased to 3.5.0
Am 30.04.2015 um 23:00 schrieb David M Williams: The current validation error has to do with common navigator, and I've seen some notes that's going to be managed and Tyme adjust (I assume with a warm up build?) But, even after that, or, if we we temporary disabled Tyme, then I think it was Oomph that will show up next with an incompatibility on o.e.core.expressions. Thanks for the hint. I've fixed the problem in Oomph, promoted a new build and submitted a simrel Gerrit review with the new repo URL. The Gerrit CI build is successful. I'm not used, yet, to the new Gerrit-based aggregation. Is there anything else I need to do? Am I supposed to +2 the review myself to have it merged? Cheers /Eike http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper ___ 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
Re: [cross-project-issues-dev] Heads-up: core.expressions has increased to 3.5.0
To those who had a wrong version range like [3.4, 3.5): Please find the bug in your process that introduced this too-narrow dependency in the first place. If a tool generated that dependency, then please file a bug for that tool. https://wiki.eclipse.org/Version_Numbering#How_to_specify_plug-in_requirements Thanks, Markus From: David M Williams david_willi...@us.ibm.com To: cross-project-issues-dev@eclipse.org Date: 2015-04-30 23:01 Subject:[cross-project-issues-dev] Heads-up: core.expressions has increased to 3.5.0 Sent by:cross-project-issues-dev-boun...@eclipse.org The current validation error has to do with common navigator, and I've seen some notes that's going to be managed and Tyme adjust (I assume with a warm up build?) But, even after that, or, if we we temporary disabled Tyme, then I think it was Oomph that will show up next with an incompatibility on o.e.core.expressions. We've increased the version to 3.5, and apparently many projects have defined a narrow range pre-req such as [3.4, 3.5). Since I've seen several conflicts with that change, thought I'd announce it now, instead of letting teams discover it one at a time. Any adjustments and warmup builds would be helpful to keep things building. Thanks, ___ 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 ___ 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
