[platform-releng-dev] Possible re-spin for new (fixed) version of EMF

[David M Williams <david_williams@xxxxxxxxxx>]

I've been told there is a bug in the new
M6 EMF that they need to fix for M6. Still waiting to here details of when
new build would be ready, but assume it'd be "by noon", or so.


I'm not sure if the bug effects us in
Platform directly. You can read bug 403093 [1] (and the bugs it points
to) if you think it might. As I understand it, one of them effect running
on Java 5 (not an issue for us, I don't believe) but the other is if you
use "long fragments" in URIs. While no one has reported a problem
in the past day or so we've been using the new EMF, that one sounds like
it could possibly cause problems for our adopters.  

But, on the other hand, we simply build
against EMF and happen to provide one version in our repo and packages,
but EPP packages, etc., will be picking up the newer version of EMF automatically
anyway. In this case, it becomes more a matter of "good release engineering"
for us to use the same version as everyone else, but not necessarily "blocking"
for us, though could be for others (e.g. XText). . 

So, unless someone thinks this bug alone
is enough to respin for, what I propose is that we not respin just for
it, but, if we find another reason to re-spin, then we include the fixed
EMF version as well. 

Comments/suggestions welcome. 

Thanks, 


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=403093