Hi Mario,
thanks, and yes actually I would be happy if you found something useful to include back into a module of drools.
Found your questions very interesting and in fact appears it's possible to make it parametric, thanks to the Velocity templates; so you can see:
- commit 4c57951 - adds parameter switch for inclusion of Eclipse-compatibility plugin in pom.xml
- commit eb371df - adds parameter switch for use of CEP features in example rules.drl and JUnit test
You will also notice the default value of the parameters are likely *the opposite* of what you may want to have in the Drools distribution, moving in the direction you suggested; but this is only because for my use-case made more sense this way. Possibly the non-CEP rule shall provide a different example... You guys let me know if I shall perform any specific action on github, or anything else further required / helpful in that direction, in case.
My perspective on archetypes is that shall be kept to the minimum as possible, both in the dimensions of qty and params; the drools-examples-api will do the rest because indeed being examples. I think we can reasonably agree on this perspective and I'm just mentioning this because, on other OS projects, I found too many archetypes available to being with was somehow confusing.
Thanks, Ciao
MM