Version 4 build

[planetf1]

Is there an existing issue for this?

• I have searched the existing issues

Please describe the new behavior that that will improve Egeria

Establish new build process for Egeria version 4

Alternatives

No response

Any Further Information?

No response

Would you be prepared to be assigned this issue to work on?

• I can work on this

[planetf1]

I'm working through getting the v4 pipelines/code working fully.

One thing to note -- this branch needs to frequently receive merges from main. In order to simplify the git log I have permitted myself to do direct pushes to the repo. This is needed to do a 'git rebase'. This effectively keeps the v4 specific changes floating on top of the other repo changes, which will keep the history synced with 'main'.

When we start work on v4 fully we can push the 4.0pre branch changes (normal merge) back to main to continue with development, and avoid having a confusing history with loads of extra merges.

This is specific to the 4.0 branch whilst in the early stages, as this is normally not a good idea, as checks can be bypassed, and history replaced.

So

• Code changes to enable v4/java 17 builds -> regular PR/merge
• Periodic update from main to refresh the v4 branch -> rebase & force push

[planetf1]

As per slack post

The Egeria v4 pipeline is now working
builds from egeria-release-4.0pre
delta - specific fixes to gradle build and github actions only
Uses gradle (only)
Uses Java 17 LTS (temurin)
FVT tests all good
running codeQL & sonatype lift
Maven Snapshots signed & published to maven central (4.0-SNAPSHOT)
Many ‘intermediate’ pom-only artifacts are removed (ie org.odpi.egeria:access-services) as their need was only driven by maven’s structure
Docker images published (4.0-SNAPSHOT)
Will rebase from main periodically.
This is part of a bigger set of steps to get to gradle/java 17 for release 4 in 2023. There is still more to do on verification. Maven removal will be left until closer to the time.
(The last fix for docker is just being merged)
I’ll do another iteration in a few weeks. After that (or perhaps Jan) we can review progress/changes in a community or dev call.

Closing this as the initial setup to allow us to refine work on v4 and fix up the gradle build is now in place