Build fails
by Michael Anstis
Clean grab from svn and build with mvn(3.1) clean install -DskipTests=true
failed on drools-compiler:-
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile
(default-testCompile) on project drools-compiler: Compilation failure:
Compilation failure:
[ERROR]
/home/manstis/workspaces/svn/drools-mvn3/trunk/drools-compiler/src/test/java/org/drools/agent/KnowledgeAgentTest.java:[132,14]
cannot find symbol
[ERROR] symbol : method
removeEventListener(org.drools.event.knowledgeagent.KnowledgeAgentEventListener)
[ERROR] location: interface org.drools.agent.KnowledgeAgent
[ERROR]
/home/manstis/workspaces/svn/drools-mvn3/trunk/drools-compiler/src/test/java/org/drools/agent/KnowledgeAgentTest.java:[181,14]
cannot find symbol
[ERROR] symbol : method
removeEventListener(org.drools.event.knowledgeagent.KnowledgeAgentEventListener)
[ERROR] location: interface org.drools.agent.KnowledgeAgent
[ERROR]
/home/manstis/workspaces/svn/drools-mvn3/trunk/drools-compiler/src/test/java/org/drools/agent/KnowledgeAgentTest.java:[230,14]
cannot find symbol
[ERROR] symbol : method
removeEventListener(org.drools.event.knowledgeagent.KnowledgeAgentEventListener)
[ERROR] location: interface org.drools.agent.KnowledgeAgent
Is there some (incomplete) work in progress to be commited?
13 years, 4 months
ClassLoader Improvements and OSGi
by Mark Proctor
I have done more cleaning up in the ClassLoader stuff.
While we added a root CompositeClassLoader recently there was still
another alternative composite ClassLoader implementation that was used
by the Packages. So we ended up with a composite CL being added to
another CL. Both composites had their own caching etc.
So now we have single CompositeClassLoader, with a single point of
caching and slightly improve coding at detecting Drools specific CLs. My
hope is that the code is also more efficient.
This work was done due to another OSGi requirement where each module
needs to add itself to the root classloader. But sometimes it was
returning the root CL, or sometimes the package level composite CL. So
now there is only one and that should no longer happen.
What this means is that any module that will have it's classes resolved
via reflection from other modules should in their constructor or other
initialisation of the code do something like
getRootClassLoader().addClassLoader( getClass().getClassLoader() ). In
situations where it's a single container all modules have the same
classloader and the call gets ignored, as it won't re-added an existing
CL. In the OSGi case it'll add the classloader and now classes from that
module can be resolved in an OSGi environment.
Mark
13 years, 4 months
KnowlegeAgent Tests
by Mark Proctor
The KnowlegeAgent tests have been fragile for a while, related to "wait"
code and file issues, particularly on windows. Something has changed
recently and now they aren't working on the linux hudson server either.
So I'm now in the process of refactoring the tests to make them more
robust, and they will hopefully run faster too, as I'll use call backs
when something has finished instead of waiting for X seconds in the hope
that something has finished.
Mark
13 years, 4 months
deprecating old core/compiler apis
by Mark Proctor
We've attempted to keep the main core/compiler api compatabile in our
codebase for our existing users, while providing the new drools-api.
However this leaves a lot of messy code and we think it's time to start
cleaning up. So anyone think it'll be a problem if stuff in core and
compiler starts to change?
Mark
13 years, 4 months