Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I was willing to contribute to a new CLIPSJNI version with the following changes:
+ More "standardized" package name (e.g. something like net.sf.clipsrules)
+ Throwing exceptions instead of printing errors on the stdout
+ Documenting the Environment class methods a little bit
+ Mavenizing the project
+ Creating an OSGi compliant jar
I have most of these points implemented in a private project but, do they all sound interesting to you guys? If so, how should I contribute to your official repo?
You can send the updates to firstname.lastname@example.org and I'll look into including them in a future update of CLIPSJNI.
Hi Gary, all,
Instead of sending you the updates, which might be a little bit harsh for you, I've forked CLIPSJNI in Github and applied the changes I told you about in the previous post in separated commits: https://github.com/gomezgoiri/CLIPSJNI
All the changes are explained there.