@Thomas: I think you just solved my problem. I had to check if profiles let
you modify and they do!
There's one issue left though, if tests and demos are left out of the
release then their versions won't be updated, which means their POMs will
have to be updated after a release.
I guess I can
How about (in addition to disabling the deploy plugin, just in case)
putting those submodules into a profile, enabled by default, but disabled
during release? (e.g. through a "-P !tests" or "-Dit-tests=false" in
and the appropriate activation for the profile)
On Fri, Feb 5, 2021 at 2:16 PM
Hi Maarten,
Yup, this is a matter of fact an attempt to configure the Layrry build to
publish its artifacts to Maven Central and make it happen with a single release
commit.
I’ve got the deploy plugin configured in such a way they it will skip tests and
examples. That works. However the
Hi Andres,
If its just about deploying the modules to a remote repo, you could set
the skip property of the maven-deploy-plugin. I've applied that trick in
a Maven plug-in I've made [1]; their integration tests don't need to be
in Central, but all other modules should. In this scenario, the
