Is there some reason that the Mule module specifies spring 3.2.x where all the other Flowable modules are using the 4.x branch?
If one hasn’t guessed by now I’m trying to make sense out of the various versions of jars that are specified in various projects and/or pulled in transitively.
The last time I checked, the Mule open source version only supported Spring 3.2.x, not Spring 4.x. But maybe they finally moved to supporting Spring 4.x as well now. Will check it.
Looking at the Mule documentaiton I find:
Supported Spring Versions
- Mule 3.8: Spring 4.1.9 and Spring Security 4.0.4
- Mule 3.7.5: Spring 4.1.9 and Spring Security 4.0.4
- Mule 3.7.0 - 3.7.4: Spring 4.1.6 and Spring Security 4.0.1
- Mule 3.6 and earlier: Spring 3.2 and Spring Security 3.0
I was successful in upping the Mule version in the root POM from 3.5.0 to 3.8.0 and spring mule version in the Mule module POM to the 4.1.9.RELEASE. I did a
mvn clean and a
mvn test successfully.
Are there other tests that need to be run?
Should I submit a PR for this change?
mvn test doesn’t run the Mule module, I believe.
You can run the module tests directly from the Mule module folder, or run “mvn -checkmule clean test” on the root.
I should have been more percise: I ran “mvn clean” in the Mule folder.
Aha In that case it sounds ok to upgrade to me.
Just submitted this PR #424 given the OK from @joram.