Bug 1292279 - Spring core version guidance/certification update
Spring core version guidance/certification update
Status: NEW
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: jBPM Core (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Maciej Swiderski
Radovan Synek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-16 16:41 EST by Josh West
Modified: 2016-01-08 16:57 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josh West 2015-12-16 16:41:34 EST
Description of problem:

Many customers choose to embed the JBPM engine in their application, and also use the spring library. They want guidance on what dependency manifest to use for their application. Currently BPMS does its certification tests with Spring Core 3.2.13.RELEASE and is the only version of Spring we can truely recommend today, which is going EOL near term.  

It is understood that we don't have Spring in our certification matrix, and don't plan to. We do educate the customers that there is a degree of flexibility there which leads to less ability to provide certainty with all the possible combinations. Nevertheless, it would still be valuable to have a newer version in the target so that we can give the customer a little more sense of certainty. This has come up at two of our biggest flagship customers for BxMS in the northeast.  

Longer term, it would even better to see a set of archetypes coming from the product team that templatize recommended dependency manifests.

Due to active project migrations waiting (or otherwise working through the dependency resolution manually) the desired target is next patch release of 6.2.x -> 6.2.1 if possible.

Note You need to log in before you can comment on or make changes to this bug.