Yes, that is not you making it fail. That's me fixing it. (I would open
a bug, since still not sure it's fixed ... but, bugzilla seems down, at
the moment).
More to the point, I appreciate your care, in both checking and
documenting the issues, and all sounds well, to me.
Thanks again,
Thanks Alexander, for letting us know. I myself won't object to your M5
timing, and since is for GEF4 (not GEF in general) I suspect all is fine,
either way.
But, I wanted to remind you, and the whole extended team, that it is
best to settle these issues as soon as possible. The reason is
Hi David, please find my comments below.
Am 24.08.2015 um 14:49 schrieb David M Williams david_willi...@us.ibm.com:
Thanks Alexander, for letting us know. I myself won't object to your M5
timing, and since is for GEF4 (not GEF in general) I suspect all is fine,
either way.
But, I
On 21.08.15 18:41, David M Williams wrote:
I do not in principle have any objection, but think you should detail a
little more about what's new, that caused the minor increase.
The problem is that e(fx)clipse has a dual life. We have a runtime and a
tooling part and the runtime part. We are
GEF4 has dependencies to org.eclipse.fx.runtime.min.feature only, not on the
tooling. We specify it as follows, so 2.1.0 should indeed be no problem from a
composition viewpoint.
import feature=org.eclipse.fx.runtime.min.feature version=2.0.0
match=greaterOrEqual“/
Of course we will still
On 24.08.15 11:35, Alexander Nyßen wrote:
GEF4 has dependencies to org.eclipse.fx.runtime.min.feature only, not on
the tooling. We specify it as follows, so 2.1.0 should indeed be no
problem from a composition viewpoint.
Hi David,
I've pushed now the changes to [1] but the verfication job is failing
[2]. I'm quite sure that it's not me who makes it fail right?
---
...
getModelFromGit:
04:53:37 [echo] execute git checkout
83a6dcdb181eaebe429ae3ca51aa87e2a4457467 in
Like I said. We are to other Eclipse Projects a leaf project where the
only known Eclipse dependency is GEF4 who is itself in incubation.
Just to clarify: GEF4 is not incubation. Its provisional API of GEF.
Cheers
Alexander
--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer
Telefon: +49
Hi,
I ran the validation locally and it succeeded, so I'm quite sure its not
my commit who makes it fail. So I think GEF4 is OK with upgrading our
version to 2.1.
Tom
On 24.08.15 10:58, Tom Schindl wrote:
Hi David,
I've pushed now the changes to [1] but the verfication job is failing
[2].
Hi David,
I'm unable to merge https://git.eclipse.org/r/#/c/54379/2 not sure
what's going on there.
Tom
On 24.08.15 14:29, David M Williams wrote:
Yes, that is not you making it fail. That's me fixing it. (I would
open a bug, since still not sure it's fixed ... but, bugzilla seems
down, at
I don't know what's wrong either ... but, have opened bug 475748 for the
Gerrit build problems.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=475748
In the mean time, it seemed you committed that for 'master' (not
Mars_maintenance) but I went ahead and submitted to master, which should
cause
Hi,
On 25.08.15 00:54, David M Williams wrote:
I don't know what's wrong either ... but, have opened bug 475748 for the
Gerrit build problems.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=475748
In the mean time, it seemed you committed that for 'master' (not
Mars_maintenance) but I went
Dear cross-projects,
I’m currently investigating ui freeze reports.
Many of those freezes are caused by loading classes or resources from zip files
inside the UI thread.
I tend to believe that those UI freezes cannot be „fixed“ by loading classes
in the background“ and also believe that these
13 matches
Mail list logo
