Re: [buckminster-dev] how to have junit available in headless buckminste

[Achim Demelt <a.demelt@xxxxxxxxxxxxx>]

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.