[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-ocl.dev] OCL 4.1M1
|
|
Hi Adolfo,
No worries, this was only a possible clue to help you get a build
anyways ^^.
As for information about this failure : I got none. Those messages
I sent on cross-projects never found an answer, so I guess that we
are the only ones affected and/or nobody knows why we might get
this failure on some slave but not on others. The dependency might
be a non-optional "derived" one that p2 manages to find on some
slaves' environment but not on others through reexports or the
such? Anyways, as long as I manage to get a green build that does
not matter much. I am reluctant to add dependencies for my plugins
though, even for "tests" ones. I'll live with tying my builds to
slaves on which they work for now :).
Laurent Goubet
Obeo
On 27/08/2012 10:58, Adolfo Sánchez-Barbudo Herrera wrote:
Hi Laurent,
Apologies for the delayed response. I've been off for holidays.
Thank you very much for the information. We have finally added the
dependency in the tests plugin.
As same as occurred when we suffered this problem, I'm simply
curious about why we might obtain these different build results
depending on the hudson slave on which we are running the build.
I guess you haven't found any clue about this, have you ?
Cheers,
Adolfo.
El 21/08/2012 9:56, Laurent Goubet
escribió:
Hi Ed,
Adolfo,
This might be the same as we see with Acceleo : http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06420.html
.
Our builds failed (and still do) on some of the slave with
cryptic errors of "*junit* not found", often with pde or jdt
namespaces. We had to tie our builds to slave1/slave6 to make
them work... might be something to try in your case too.
Laurent Goubet
Obeo
On 20/08/2012 17:47, Ed Willink wrote:
Hi Adolfo
The branch tests build has suddenly
started to fail because org.eclipse.jdt.junit.runtime is not
in the workspace; it isn't and never was and isn't in the
plug-in requirements. Perhaps JDT/JUnit support has suddenly
exposed an assumption.
Just did a QVTo build and org.eclipse.jdt.junit.runtime was
loaded into the workspace. But it bombs on
org.eclipse.pde.junit.runtime instead.
Regards
Ed Willink
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
begin:vcard
fn:Laurent Goubet
n:Goubet;Laurent
org:<a href="http://www.obeo.fr";>Obeo</a>
email;internet:laurent.goubet@xxxxxxx
url:http://www.obeo.fr
version:2.1
end:vcard
