The tree goal is my go to for this plugin. I also like the analyze.
A wish I have is to get a more clearer view of the resolved dependencies
version with regard to the declared dependencyManagement and/or the
shortest path to dependency.
For example, when I see the dependency slf4j-api with
I'm not talking about the -T option, I'm talking about running 2 builds in
parallel, something like
cd /some/repo1
mvn clean verify &
cd /some/repo2
mvn clean verify &
It could also be your IDE auto building too, I've seen that happen.
On Fri, Feb 18, 2022 at 11:13 AM Nils Breunese wrote:
>
trunk based vs gitflow is a well covered subject on the internet, both have
tradeoffs that you need to think about and choose what's best for you.
For us, it was the ability to quickly make a hotfix on the master branch
for production in case a big refactor/change was merged in the develop
branch
We use gitflow so a develop branch with "1-SNAPSHOT" version and a master
branch with a fixed maven version in it. We have a script to handle the
merge from develop->master and bump the appropriate version based on the
previous one. It's all automated in a script that is run on jenkins to be
able
Hi Dave,
Does this maven-release part of your workflow runs on CI? If yes, you can
manually allow specific users to push directly to master, that's what we do
on our end. We have a specific restricted CI user that we manually allow on
the branch permissions in bitbucket with write access and keep
Hey,
There might be other ways to do this but what I did was I built a custom
image with some special configuration. You could also try mounting a volume
to the /lib directory (something like
Hi!
I have been testing and using the redis locks implementation of Maven
Resolver 1.6.x on 3.8.x for a while now on my CI instances. It works great
but I would like to follow the development/bugfixes of it and saw that it
was all happening on the 1.7.x which is built with Java 8 and therefore
