Once the IdP V 4.2 is release we should move the parent poms use by the enforcer and enforcer-data projects forwards (they are referenced by the java-parent project and so have to move after a release).
mvn-enforcer should move to idp-parent:4.2.0 and mvn-enforcer-data should move to parent:11.3.0
We should also pop a .checkm2 file into the repositories (and adjust the CI builds to turn it off) so that future builds do a self check (if feasible - always noting that in particular for the data there is a bootstrap issue - if we cannot do a release because we don’t have the data we cannot release the data…)
Once the IdP V 4.2 is release we should move the parent poms use by the enforcer and enforcer-data projects forwards (they are referenced by the java-parent project and so have to move after a release).
mvn-enforcer should move to
idp-parent:4.2.0and mvn-enforcer-data should move toparent:11.3.0We should also pop a
.checkm2file into the repositories (and adjust the CI builds to turn it off) so that future builds do a self check (if feasible - always noting that in particular for the data there is a bootstrap issue - if we cannot do a release because we don’t have the data we cannot release the data…)