<div>I will try to fix all tests for the eclipse-plugin as soon as possible (hope I can get them working tonight).</div>
<div>So that includes uncommenting tests again, making sure they compile and making sure they are executed succesfully.</div>
<div> </div>
<div>Kris<br> </div>
<div><span class="gmail_quote">On 4/4/07, <b class="gmail_sendername">Mark Proctor</b> <<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Also not only are many tests commented out, but most tests fail, would<br>be good if we can sort this out.
<br><br>Mark<br>Mark Proctor wrote:<br>> Just a reminder that I have refactored the eclipse stuff and there are<br>> now four directories.under drools-eclipse, drools-ide no long exists.<br>> drools-eclipse-plugin
<br>> drools-eclipse-feature<br>> drools-eclipse-test<br>> drools-eclipse-test-feature<br>><br>> We are gradually fully automating and customising maven so the top<br>> level build.xml will be killed off. soon, and most likely no longer
<br>> works. However ant is still used to build the documentation and the<br>> eclipse plugin, it is just integrated into the mavne lifecycle using<br>> the antrun plugin.<br>><br>> We will continue include the engine, eclipse and brms in the same
<br>> build system for now as the project is quite fluid and we need close<br>> co-operation. In the future, when the engine api and language features<br>> mature, we may look at seperating brms and eclipse, or atleast the
<br>> brms, so that they baseline with a specific version of the engine<br>> release, this will allow projects to do releases on their own.<br>><br>> I have automed the eclipse plugin build, although still trying to get
<br>> the unit tests automated, and that is now part of the maven life<br>> cycle. Edson is currently investigating having the various ant and<br>> manfiest files having their information populated from maven - i.e
.<br>> dependencies and version info.<br>><br>> drools-eclipse is now activated as a profile, using the eclipse.home<br>> settings, this is part of the automation process and the libs will not<br>> be copied across unless you do this.
<br>> mvn -Dmaven.test.skip -Declipse.home=c:\java\eclipse install<br>><br>> The following classes have commented out tests, can I ask who ever is<br>> responsible for them to sort this out. I want to get the eclipse
<br>> automation and testing ship shape, which will make things easier for<br>> the future.<br>> IncompleteParsingTest<br>> ReteooLayoutFactoryTest<br>> RuleContentOutlineTest<br>><br>> Mark<br>> _______________________________________________
<br>> rules-dev mailing list<br>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev
</a><br>><br><br></blockquote></div><br>