I will try and describe what I know (and perhaps a README would make more
sense?)
On Wed, Oct 27, 2010 at 8:57 AM, Michael Anstis <michael.anstis(a)gmail.com>wrote:
Hi Geoffrey,
Being relatively new I can't comment on some of the specifics, but I
question the following:-
- drools-assistant
Hmm... is this the refactoring support project? If so - not sure what
state it was
in. This was a google summer of code thing if I am not
mistaken.
- drools-atom
Can retire - was an atom-module for Guvnor for atompub support (what little
atom is
needed is now baked in anyway).
- drools-clips (I believe Mark did this on a rainy weekend, but don't
know if it's still supported).
HAhaha - I believe that started in a pub, and then mark did a furious
amount of
work - made it work in, what, 2007 (it is/was pretty cool
actually)? Last I looked at it, I added a little shell... but if its not
maintained at the moment up to all drools features - I still think it should
stay around - as it may matter to someone enough to get it up to date if it
isn't (help with people coming from jess for instance).
- drools-container
- drools-doc\drools-docs (which is actively used?!? Do we need both?)
- drools-rhq-plugin
I think Edson (?) did this - or Heiko Rupp? this is legitimate probably -
but
really should shift to the
rhq-project.org repository - not live in
drools in my opinion.
-
- drools-simulator
- install
- src
I have thought for a long time I'd be good to have on the Wiki a summary of
what each project represents and what package (JAR) they bundle into.
Cheers,
Mike
On 26 October 2010 15:59, Geoffrey De Smet <ge0ffrey.spam(a)gmail.com>wrote:
> 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.
>
> --
> With kind regards,
> Geoffrey De Smet
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
>
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
--
Michael D Neale
home:
www.michaelneale.net
blog:
michaelneale.blogspot.com