brms and repository directory
by Mark Proctor
The clean code in the brms module is also cleaning the root repository
directory. I have renamed the root one to m2_repo to avoid the
collision, but could someone change the pom to make sure its more
specific than it is now.
Mark
17 years
drools-eclipse
by Mark Proctor
Kris,
Good news all the tests now work, except the ZoomControlTest which says
"workspace is closed" for both tests. Maybe philippe can assist here.
Mark
Kris Verlaenen wrote:
> I think I now commited everything for getting the tests working as
> they are now.
> Also added 2 fixes for 2 JIRAs (the nullpointer in outline and the
> codecompletion of static classes), and some fixes for the DSL editor,
> which didn't work anymore after refactoring core and was in urgent
> need of some stability control (was generating errors at numerous
> places when clicking buttons you shouldn't).
>
> Kris
>
>
> On 4/6/07, *Mark Proctor* <mproctor(a)codehaus.org
> <mailto:mproctor@codehaus.org>> wrote:
>
> Kris,
>
> Any luck with those commits?
>
> Mark
>
>
17 years
Problem in running rules file from command line
by Sudipta Deb
I am facing some problem when i am trying to do this. I am new to JBoss can
anybody please help me.
In a folder i copied HelloWorldExample.java & HelloWorld.drl and changed the
code to eliminate the package line
Next i changed the classpath and include different jar files required for
rule like drools-core.jar, ....
Compilation was absolutely fine
but when i am going to run the program the error is :
java.lang.NoClassDefFoundException . Didn't get it why this exception is
coming.
I want to run the java file from command line like in this was javac
HelloWorldExample not from eclipse.
Please help me
--
View this message in context: http://www.nabble.com/Problem-in-running-rules-file-from-command-line-tf3...
Sent from the drools - dev mailing list archive at Nabble.com.
17 years
Re: [rules-dev] drools-eclipse
by Mark Proctor
I have two unit tests failing to compiler still:
DRLCompletionProcessTest is failing becuase
"DefaultCompletionProcessor.filterProposalsOnPrefix" is not a static
method call. Which is confirmed here
http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-eclipse/drools...
RuleContentOutlinePage is failing because page.populatePackageTreeNode(
source ) does not expect a parameter. Which is confirmed here
http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-eclipse/drools...
When doing "run as junit" inside eclipse the ZoomControlTests fail,
"worspace closed".
LocationDeterminatorTest has a failure for
"testCheckLocationDetermination" "expected <2> but was: <1>
Mark
Kris Verlaenen wrote:
> I have now fixed most tests, at least they seem to be running here
> locally.
> Note that one of the tests (ZoomControlTest) is actually a plugin
> test, not sure if you can run those within the automatic build, as
> they need the eclipse IDE to startup when testing (not sure, maybe
> maven has support for eclipse plugin unit tests?). Not sure how
> important that test is (I commented out some lines to get it working,
> I'll fix that later).
>
> Let me know if you need more help in getting the build for the
> eclipse-plugin integrated in the overall build.
>
> Kris
>
> On 4/5/07, *Kris Verlaenen* <kris.verlaenen(a)gmail.com
> <mailto:kris.verlaenen@gmail.com>> wrote:
>
> I will try to fix all tests for the eclipse-plugin as soon as
> possible (hope I can get them working tonight).
> So that includes uncommenting tests again, making sure they
> compile and making sure they are executed succesfully.
>
> Kris
>
> On 4/4/07, *Mark Proctor* <mproctor(a)codehaus.org
> <mailto:mproctor@codehaus.org>> wrote:
>
> Also not only are many tests commented out, but most tests
> fail, would
> be good if we can sort this out.
>
> Mark
> Mark Proctor wrote:
> > Just a reminder that I have refactored the eclipse stuff and
> there are
> > now four directories.under drools-eclipse, drools-ide no long
> exists.
> > drools-eclipse-plugin
> > drools-eclipse-feature
> > drools-eclipse-test
> > drools-eclipse-test-feature
> >
> > We are gradually fully automating and customising maven so
> the top
> > level build.xml will be killed off. soon, and most likely no
> longer
> > works. However ant is still used to build the documentation
> and the
> > eclipse plugin, it is just integrated into the mavne
> lifecycle using
> > the antrun plugin.
> >
> > We will continue include the engine, eclipse and brms in the
> same
> > build system for now as the project is quite fluid and we
> need close
> > co-operation. In the future, when the engine api and language
> features
> > mature, we may look at seperating brms and eclipse, or
> atleast the
> > brms, so that they baseline with a specific version of the engine
> > release, this will allow projects to do releases on their own.
> >
> > I have automed the eclipse plugin build, although still
> trying to get
> > the unit tests automated, and that is now part of the maven life
> > cycle. Edson is currently investigating having the various
> ant and
> > manfiest files having their information populated from maven
> - i.e .
> > dependencies and version info.
> >
> > drools-eclipse is now activated as a profile, using the
> eclipse.home
> > settings, this is part of the automation process and the libs
> will not
> > be copied across unless you do this.
> > mvn -Dmaven.test.skip -Declipse.home=c:\java\eclipse install
> >
> > The following classes have commented out tests, can I ask who
> ever is
> > responsible for them to sort this out. I want to get the eclipse
> > automation and testing ship shape, which will make things
> easier for
> > the future.
> > IncompleteParsingTest
> > ReteooLayoutFactoryTest
> > RuleContentOutlineTest
> >
> > Mark
> > _______________________________________________
> > rules-dev mailing list
> > rules-dev(a)lists.jboss.org <mailto:rules-dev@lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/rules-dev
> <https://lists.jboss.org/mailman/listinfo/rules-dev>
> >
>
>
>
17 years
drools-eclipse
by Mark Proctor
Just a reminder that I have refactored the eclipse stuff and there are
now four directories.under drools-eclipse, drools-ide no long exists.
drools-eclipse-plugin
drools-eclipse-feature
drools-eclipse-test
drools-eclipse-test-feature
We are gradually fully automating and customising maven so the top level
build.xml will be killed off. soon, and most likely no longer works.
However ant is still used to build the documentation and the eclipse
plugin, it is just integrated into the mavne lifecycle using the antrun
plugin.
We will continue include the engine, eclipse and brms in the same build
system for now as the project is quite fluid and we need close
co-operation. In the future, when the engine api and language features
mature, we may look at seperating brms and eclipse, or atleast the brms,
so that they baseline with a specific version of the engine release,
this will allow projects to do releases on their own.
I have automed the eclipse plugin build, although still trying to get
the unit tests automated, and that is now part of the maven life cycle.
Edson is currently investigating having the various ant and manfiest
files having their information populated from maven - i.e. dependencies
and version info.
drools-eclipse is now activated as a profile, using the eclipse.home
settings, this is part of the automation process and the libs will not
be copied across unless you do this.
mvn -Dmaven.test.skip -Declipse.home=c:\java\eclipse install
The following classes have commented out tests, can I ask who ever is
responsible for them to sort this out. I want to get the eclipse
automation and testing ship shape, which will make things easier for the
future.
IncompleteParsingTest
ReteooLayoutFactoryTest
RuleContentOutlineTest
Mark
17 years
Rules Modelling with UML
by Javier Chamizo Aguado
Hello all,
I am looking for references about ways of modelling business rules in UML
but dont find anything.
Could anyone give a hint about where and what to look for?
Thank you very much
Javier
17 years
