poms-shared

The java domain classes used by NPO Frontend API, POMS Backend and other POMS projects.

These are also used by the API clients.

See also poms parent

build

This is automatically build on github.

Basically it’s just

michiel@mitulo:~/github/npo-poms/poms-shared$ mvn
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] poms shared                                                        [pom]
[INFO] poms-shared-domain                                                 [jar]
[INFO] poms-shared                                                        [jar]
[INFO] user-domain                                                        [jar]
...

The github build can be done locally with 'act'. Create a file '${USER.HOME}/.secrets' (a propertyfile with the secrets of this project) and then:

michiel@mitulo:~/github/npo-poms/poms-shared$ act
[build/build] 🚀  Start image=nektos/act-environments-ubuntu:18.04
[build/build]   🐳  docker run image=nektos/act-environments-ubuntu:18.04 platform= entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[build/build]   🐳  docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root
...

Compatibility

poms shared	java	remarks
4.x	java 8
5.x	java 8
6.x	java 8	openshift, used by VPRO cinema backend
7.x	java 11
7.2	java 11	used by VPRO magnolia (which is currently classified as abandon ware)
>= 7.7	java 17	august 2023
7.11-SNAPSHOT branch	latest javax branch. Minor releases can be made from this. >= 7.12 must be branched from this, not from main	february 2024
7.12-SNAPSHOT branch	used for poms 7.12 released. Doesn’t contain some changed related to hibernate-search upgrade (media sort field methods)	may 2024
8.x	javax - > jakarta	february 2024
8.2	hibernate 6	may 2024, hibernate is only an optional dependency (only the annotations are used in this project)
9.x	java 21	late 2024

Maven versioning

We are in a kind of hybrid situation For main we use 'CI friendly' versioning (using revision and changelist properties).

For release branches this is overridden by the release:branch plugin

This means that open pull requests (on main) will result in artifacts on sonatype snapshots that have the name of the branch in their version. They can be used in associated merge requests in other projects (likely one of the poms projects in the VPRO gitlab repository)

Releasing

Make sure SNAPSHOT are resolved. Furthermore, it’s similar to as described in poms parent.

See actions