The following table shows the compatibility between different versions of Drools, jBPM and Guvnor.
If you combine the versions specified in any single row of this table, they are compatible
Hi,
I've decided to build my own Knowledge OSGi bundle to be able to test the latest things of Drools and JBPM. Now I have some puzzle is in my head that I would like someone clarifying me.
Looking at the master branch of the droolsjbpm-parent project, which is in version 5.4.0-SNAPSHOT, I could see this in its POM:
<!-- Internal dependencies -->and at the master branch of the jbpm project, I could see this in its POM:
<drools.version>5.4.0-SNAPSHOT</drools.version>
<drools.osgi.version>5.4.0.SNAPSHOT</drools.osgi.version>
<drools-planner.version>${drools.version}</drools-planner.version>
<jbpm.version>5.2.0.Final</jbpm.version>
<jbpm.osgi.version>5.2.0.Final</jbpm.osgi.version>
<parent>
<groupId>org.drools</groupId>
<artifactId>droolsjbpm-parent</artifactId>
<version>5.3.2-SNAPSHOT</version>
<!-- relativePath causes out-of-date problems on hudson slaves -->
<!--<relativePath>../droolsjbpm-build-bootstrap/pom.xml</relativePath>-->
</parent>
and at the master branch of the drools project, in its POM I could see this:
<parent>
<groupId>org.drools</groupId>
<artifactId>droolsjbpm-parent</artifactId>
<version>5.4.0-SNAPSHOT</version>
<!-- relativePath causes out-of-date problems on hudson slaves -->
<!--<relativePath>../droolsjbpm-build-bootstrap/pom.xml</relativePath>-->
</parent>
Could someone explain me the choose release cycle and the relationship of the these projects: droolsjbpm-parent, drools, jbpm ?
I think that I read once that JBPM 5 runs on top of Drools and that both has different release cycles, but shouldn't Jbpm SNAPSHOT, once it is a snapshot, always use the latest version of droolsjbpm-parent and consequently the latest of Drools too ?
regards
Cristiano
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
-- With kind regards, Geoffrey De Smet