Moqui 4.0 Initiative and PRs

Technical Discussion
1

Creating this topic to consolidate all my work on upgrading and overhauling moqui to prepare for version 4.0. The highlights are the following

  • I have forked and taken over development of the bitronix transaction manager. I created our first version v4.0.0-BETA1 with massive changees that modernize bitronix and makes it compatible with newer versions of Java (17+)
  • Upgraded moqui in terms of gradle and Java with lots of fixes to both the framework AND the community components. I have detailed the work in the release notes
  • Also deleted the bitronix jar and now depend on the github version (to publish later perhaps to mavenCentral)

I have documented in these links everything including remaining work. Feel free to review.

My pull request for all this work are as follows:

1 Like
2

OH I forgot to mention. ElasticSearch must go! It’s incompatible with newer Java, and divergence is happening between elasticsearch and opensearch. It’s better to drop support completely and move to opensearch. I didn’t do any of the work pending discussions first.

3

Let’s talk about this on the next Moqui call for sure.

4

@taher I merged all the PRs into an upgrade branch.

5

Hi @michael

Thank you, I also created another Testing PR that covers the following:

  • First I enable unit tests, the task was not running due to gradle 9 changes
  • I created convenience methods testComponents (all components) and testAll (everything).
  • I fixed one failing test, however, 14 tests are still failing not to mention component test failures.

Overall I think we should take testing more seriously, fix all tests (some seem to be broken long ago) and we need to automate this to get more confidence out of the code base.