Important Breaking Upgrades

Community Development
1

Hello Community ,
Following the Release of 3.1.0.4 ,
We are soon going to do an Upgrade (3.2.0.0) that will be breaking your existing PRs and Local changes.
The Upgrade involves upgrading to Java 21 ,Tomcat 10 , Spring 6.x , hiberanate 6.x , Jarkata EE api

What to do

  1. You will Upgrade to Java 21

  2. The main breaking change is the Java EE upgrade
    Youll have to update your imports from javax to jarkata. ie

    Old (Java EE / javax) New (Jakarta EE 9+)
    javax.servlet.* jakarta.servlet.*
    javax.persistence.* jakarta.persistence.*
    javax.validation.* jakarta.validation.*
    javax.xml.bind.* jakarta.xml.bind.*

Note that the rest of the development process remains the same .

The current verion (3.1.0.4) will be mantained on branch 3.1.x

cc @caseyi @calebslane @Herbert @reagan

6 Likes
3

Noted ! @Moses_Mutesasira thanx for update !
This means the next changes we are to push should be redirected to branch 3.1.x

4

thanks @Moses_Mutesasira and the team for the updates,

5

Thanks for the update!!

6

Not really , we will still be working on develop and only back port impontant fixes to 3.1.x

4 Likes
7

thank you for the updates

8

The Breaking changes have been merged.

To update your local dev enviroment , first follow these steps listed above

Then

  1. Pull the latest merged changes
    git pull origin

  2. Pull the latest docker changes ,because we made chages to the base webb app image
    docker-compose -f dev.docker-compose.yml pull oe.openelis.org

Then Follow the usual dev steps

2 Likes
9

the most important thing to take caution of is that you cant rebuild with the existing submodules
we first remove the existing sub modules

git submodule deinit -f .
rm -rf .git/modules/

then update the submodules following the new changes

git submodule update --init --recursive

then follow the rest of the procedure in the readme

3 Likes
10

Thanks @Agaba_Derrick_Junior for the catch.
The submodules were updated too

1 Like