Am 31.07.2020 um 10:56 schrieb Konrad Windszus:
Hi,
currently the check-release.sh
(https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh) executes the Maven
build in step 6. with "mvn clean verify".
That means if one releases couples multiple dependent modules one has to
install the dependent module in the local Maven repository
(https://lists.apache.org/thread.html/rc2dad58b0f6817ccadc77ec8fe09b47b9a1c22505e90dd523df70617%40%3Cdev.jackrabbit.apache.org%3E)
or reference them from the staging repository.
The latter requires adjusting the pom.xml (passing something like
"maven.repo.remote" is no longer supported with Maven2+). The former requires
adding those to the local repo.
As installing to the local repo is less effort and doesn't require passing the staging repository
to check-release.sh I would propose to adjust step 6 in check-release.sh to execute "mvn clean
install" instead of "mvn clean verify"
WDYT?
The downside is that the user might end up with a local artefact that
will not be released, or even worse, might get released with different
contents.
This might be fixable by modifiying settings.xml and adding a profile
(but probably wouldn't fly because we don't want people to have to mess
around with their condig).
Q: so why does this work when we do multi-module releases in Jackrabbit
Classic or Oak?
Best regards, Julian
