Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [emft-dev] May service releases explicitely require other service releases?

Even if binary compatible I don't quite understand why one service release may not depend on another. Assuming a project had some workarounds or had to disable certain features due to bugs in required projects: If these bugs were fixed in the SR, why shouldn't the dependencies be explicit about this?

Regards,
Sebastian


On 25.09.2010, at 10:25, Sven Efftinge wrote:

Yes, I think you are right. It's not good practice and a fault on our side.
Service releases should (and are in the case of MWE2 and Xtext) of course be binary compatible.

Sorry for this,
Sven

On Sep 25, 2010, at 8:27 AM, Eike Stepper wrote:

Hi,

emf-dev and emft-dev are CC'ed because MWE2 is related.

I've just been asked by p2 to update some features with new versions from Helios SR1. Xtext 1.0.1 was among them, but I already know that I can not update to this Xtext version (has caused me 2 days to find out why, but that's another story). No problem so far, I just unchecked Xtext.

But then it turned out that the remaining update request could not be completed because MWE2 explicitely requires a service release version of Xtext:

    org.eclipse.xtext;bundle-version="1.0.1"

I wonder if that should generally be considered bad for service releases. What do you think?


_______________________________________________
emft-dev mailing list
emft-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emft-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top