This content has been marked as final. Show 3 replies
I've been considering what to do about the jBPM Facelets component library for the upcoming release, and I think it would be best to move it out of the new repository and into the current jBPM CVS repository. This allows the component library to track with jBPM releases and will make bug fixing and maintenance easier overall.
+1. good idea.
So, I want to make the following changes:
* Add a jbpm4jsf subproject into the main CVS repository
* Update the build system so that jbpm4jsf is built by default, and include it as a project dependency rather than as an external JAR
Any objections or opinions?
please, do it as a new subproject of jbpm.3 in the same style as the other subprojects. if your problem is the build scripts, i can help you with those if you want.
OK, I've moved these in. I've also integrated with the main build system, and it looks like everything is building OK for me. Let me know if anyone runs across any major problems.
i'll give it a try