I am currently debugging a failure I am finding within Soteria as I add support for MicroProfile JWT to WildFly, I think I will be submitting a minor fix as a PR shortly but I just wanted to check what is the status of the branches in the Git repo.
Firstly the default branch is 'master' but that is still producing javax artefacts instead of jakarta artefacts. Generally in a git repository the default branch is where you would expect ongoing upstream development to occur but this branch is behind the latest release.
Next we have the EE4J_8 branch, this does seem to be producing jakarta artefacts but the version is currently 1.0.1-SNAPSHOT so effectively behind the current release.
Finally there is a 1.0.1 branch, this appears to have further commits added to move it after the 1.0.1 release but has no SNAPSHOT qualifier which is generally something you would expect if the branch is an active development branch to avoid accidentally populating with intermediate builds that are not qualified as being a SNAPSHOT build.
Additionally if the latter branch is intended to be an ongoing maintenance branch wouldn't a name like "1.0.x" or "1.0" be more appropriate?
So I think primarily I am trying to identify where to submit fixes for 1.0.x releases but also if there is any upstream synchronisation to consider.
Personally I am a fan of using `git merge` to synchronise between maintenance branches and active development branches but I know within the industry there is still a preference to manually porting commits between branches.
Regards,
Darran Lofthouse.
