Hi, Ernesto,
I don’t know if I’ve seen many builds in the tooling area fail with missing files from dependencies’ repositories, but I see that a lot in running Oomph setups. Usually just trying the setup again works, so they seem to be one-off network glitches or something. Not a domain that I understand much. No repository found maybe is a similar problem, in which a build is being published to a permanent update site URL so there’s a brief window in which resources are being replaced and so aren’t available?
The p2 profile error I haven’t seen in recent memory.
Not exactly a helpful answer, I suppose.
cW
On 6 September, 2016 at 14:13:43, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Hi. I've noticed that our nightly codegen builds have been
failing lately, but not in a consistent fashion. Sometimes they
succeed. The error logs (attached), when it fails, suggest that it
is not due to anything from codegen, but rather from Eclipse
itself. For example, some exceptions point to missing files from
org.eclipse.ecf or org.eclipse.e4.ui.workbench. Others are like
this:
Root exception:
java.lang.IllegalStateException:
Profile SDKProfile is not current. E
And one is
Have any of these errors been observed in other
components?
Could it be an issue of timing? Perhaps the problems occur
when other Eclipse projects are updating their repos?
Any ideas?
Thanks.
--
Ernesto Posse
Zeligsoft
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
