Home » Eclipse Projects » Buckminster dev » [buckminster-dev] how to have junit available in headless buckminster
| [buckminster-dev] how to have junit available in headless buckminster [message #355351] |
Tue, 28 July 2009 11:30  |
Eclipse User |
|
|
|
Originally posted by: dieter.cailliau.barco.com
This is a multi-part message in MIME format.
------_=_NextPart_001_01CA0F76.CF5DE639
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In our source tree, the junit tests are in the same bundle as the =
regular code (though in a src-test/ folder).
The manifest.mf does not depend on a junit bundle.
The workspace compiles with an IDE, thanks to .classpath files having =
this line:
<classpathentry kind=3D"con" =
path=3D"org.eclipse.jdt.junit.JUNIT_CONTAINER/4"/>
When i try to invoke a buckminster build on such a workspace i get
Error: file /tmp/ws/plugins/com....Test.java, line 17: The method =
assertTrue(boolean) is undefined for the type ...Test
Error: file /tmp/ws/plugins/com....Test.java, line 28: The method =
assertNotNull(EmptyBeanFace) is undefined for the type ...Test
Error: file /tmp/ws/plugins/com....Test.java, line 10: The hierarchy of =
the type ...Test is inconsistent
etc.=20
I don't know where to tackle this problem:=20
- is it a matter of extending the headless buckminster with some =
junit-awareness,=20
- or is something missing from my target definition,=20
- or is something wrong with my bundle structure and the usage of the =
..classpath file?
DISCLAIMER:
Unless indicated otherwise, the information contained in this message is =
privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.
------_=_NextPart_001_01CA0F76.CF5DE639
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>how to have junit available in headless buckminster</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>In our source tree, the junit tests are in the same =
bundle as the regular code (though in a src-test/ folder).<BR>
The manifest.mf does not depend on a junit bundle.<BR>
The workspace compiles with an IDE, thanks to .classpath files having =
this line:<BR>
<classpathentry kind=3D"con" =
path=3D"org.eclipse.jdt.junit.JUNIT_CONTAINER/4& ;quot;/> <BR>
<BR>
When i try to invoke a buckminster build on such a workspace i get<BR>
<BR>
Error: file /tmp/ws/plugins/com....Test.java, line 17: The method =
assertTrue(boolean) is undefined for the type ...Test<BR>
Error: file /tmp/ws/plugins/com....Test.java, line 28: The method =
assertNotNull(EmptyBeanFace) is undefined for the type ...Test<BR>
Error: file /tmp/ws/plugins/com....Test.java, line 10: The hierarchy of =
the type ...Test is inconsistent<BR>
<BR>
etc.<BR>
<BR>
I don't know where to tackle this problem:<BR>
- is it a matter of extending the headless buckminster with some =
junit-awareness,<BR>
- or is something missing from my target definition,<BR>
- or is something wrong with my bundle structure and the usage of the =
..classpath file?</FONT>
</P>
<p></p><p>DISCLAIMER:<br>Unless indicated otherwise, the information =
contained in this message is privileged and confidential, and is =
intended only for the use of the addressee(s) named above and others who =
have been specifically authorized to receive it. If you are not the =
intended recipient, you are hereby notified that any dissemination, =
distribution or copying of this message and/or attachments is strictly =
prohibited. The company accepts no liability for any damage caused by =
any virus transmitted by this email. Furthermore, the company does not =
warrant a proper and complete transmission of this information, nor does =
it accept liability for any delays. If you have received this message in =
error, please contact the sender and delete the message. Thank =
you.</BODY>
</HTML>
------_=_NextPart_001_01CA0F76.CF5DE639--
|
|
|
| Re: [buckminster-dev] how to have junit available in headless buckminster [message #356031 is a reply to message #355351] |
Tue, 28 July 2009 11:49  |
 Achim Demelt
Messages: 160
Registered: July 2009 |
Senior Member |
|
|
Dieter,
Due to technical reasons, we currently cannot include the
org.eclipse.jdt.junit plug-in in the headless environment. It has
dependencies on UI code. Without this plug-in, the
org.eclipse.jdt.junit.JUNIT_CONTAINER/4 classpath entry cannot be resolved,
and that's why your build fails.
We're working on this problem together with the JDT and PDE teams. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=278844 . I honestly don't know
when we'll be able to provide early integration builds that can provide
headless JUnit capabilities. If you want to stay up-to-date, I suggest CCing
yourself to the bug mentioned above, as well as
https://bugs.eclipse.org/bugs/show_bug.cgi?id=278845 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=243293 .
The only workaround currently available is to explicitly include the
junit.jar in your classpath.
Regards,
Achim
Cailliau, Dieter wrote:
> In our source tree, the junit tests are in the same bundle as the regular
> code (though in a src-test/ folder). The manifest.mf does not depend on a
> junit bundle. The workspace compiles with an IDE, thanks to .classpath
> files having this line: <classpathentry kind="con"
> path="org.eclipse.jdt.junit.JUNIT_CONTAINER/4"/>
>
> When i try to invoke a buckminster build on such a workspace i get
>
> Error: file /tmp/ws/plugins/com....Test.java, line 17: The method
> assertTrue(boolean) is undefined for the type ...Test Error: file
> /tmp/ws/plugins/com....Test.java, line 28: The method
> assertNotNull(EmptyBeanFace) is undefined for the type ...Test Error: file
> /tmp/ws/plugins/com....Test.java, line 10: The hierarchy of the type
> ...Test is inconsistent
>
> etc.
>
> I don't know where to tackle this problem:
> - is it a matter of extending the headless buckminster with some
> junit-awareness, - or is something missing from my target definition,
> - or is something wrong with my bundle structure and the usage of the
> .classpath file?
>
>
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message is
> privileged and confidential, and is intended only for the use of the
> addressee(s) named above and others who have been specifically authorized
> to receive it. If you are not the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this message
> and/or attachments is strictly prohibited. The company accepts no
> liability for any damage caused by any virus transmitted by this email.
> Furthermore, the company does not warrant a proper and complete
> transmission of this information, nor does it accept liability for any
> delays. If you have received this message in error, please contact the
> sender and delete the message. Thank you.
|
|
|
Goto Forum:
Current Time: Fri Apr 26 16:29:41 GMT 2024
Powered by FUDForum. Page generated in 0.03431 seconds |
] 
Search
Help
Register
Login
Home
