drools-assistant is the module that I created to add refactoring support in the eclipse plugin/guvnor. The last weekend I fixed the integration with eclipse and they will be commited in the next days, maybe tomorrow :)
I am looking at cleaning up the build and moving to maven 3,
to make it
faster, more reliable, etc.
I am also actively wondering if some modules or files aren't
dead code.
First candidate is drools-atom:
The module drools-atom is in limbo:
- It still exists
- It's not part of any build
- Does it still build? No
-- 'dependencies.dependency.version' is missing for
org.apache.cxf:cxf-rt-frontend-jaxrs:jar
- Does it still compile against the latest drools version?
Idunno, but
since it's not part of the build, tomorrow's refactor might
break it.
- Does anyone use it? If it doesn't build and it isn't
released... no?
I don't think that code is useful to anyone in this state. I
do think
it's presence alone slightly complicates the drools sources.
What do we do with it?
- [A] remove the directory drools-atom from trunk (it's still
retired in
in subversion)
- [B] leave it like it is now. It might be usefull to someone
- [C] add it to the build again, make it work
- [D] create a separate repository "drools-incubator" and move
it there
In my opinion:
+1 for [A]
-1 for [B]: either it builds or it's not in trunk
If we all agree that removing dead modules is a good idea, I
'll provide
a list of possible candidates next time.