[jbpm-dev] [Design of JBoss jBPM] - jBPM project structure and direction

thomas.diesler@jboss.com do-not-reply at jboss.com
Fri Sep 26 04:00:48 EDT 2008


Folks,

as you might know already, we wanted to give the jBPM project a more professional infrastructure that allows us to work more effectively and regularly produce the quality releases that you would expect from a jboss project. Generally, as with all other jboss projects the formula holds 


  |       project == product
  | 

Currently we have two branches of the jBPM project

jBPM3: http://anonsvn.jboss.org/repos/jbpm/jbpm3
jBPM4: http://anonsvn.jboss.org/repos/jbpm/jbpm4

jBPM3 is the codebase that is currently in production and will be maintained for the lifetime of these production releases (i.e. 5 years). The next jBPM3 release, which is jbpm-3.3.0 will come out 1-Nov-2008 and will improve on productization aspects 

* SVN code repository
* Maven build system
* Automated Hudson QA http://jbpm.dyndns.org:8280/hudson/job/jBPM-Matrix
* Defined set of target containers http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedTargetContainers
* Defined set of target databases http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedTargetDatabases
* Defined set of supported JDK's (see Hudson Matrix)
* IzPack based installer http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3BuildingTheInstaller

in jBPM4 we removed the notion of separate jPDL, PVM projects. It is all jBPM4 now. The next jBPM4 release, which is jbpm-4.0.0-Alpha1 will also come out 1-Nov-2008 and is about setting up the project infrastructure that, as I mentioned above already, will allow us to work effectively. You will also have

* SVN code repository
* Maven build system
* Automated Hudson QA http://jbpm.dyndns.org:8180/hudson/job/jBPM-Matrix

Additionally to that we are going to start an API+CTS effort, that will introduce a stable public API that jBPM clients can interact with. Maybe not so obvious clients are ESB, Management Console, BI/BAM, Test Environments, Graphical designer, etc. Every concept that we introduce in the API will be verified in a compatibility test suite (CTS). Starting in November, you should see regular design discussions about the API in this forum.

Following on from the 1-Nov release you should expect to see regular jBPM releases every 8 weeks.

cheers

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178982#4178982

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178982



More information about the jbpm-dev mailing list