Hi Marco,
I have 2 thoughts reading your post:
1. Should be enforced by an extension (sonatype plugin if target is
central?)
2. It likely misses a few phases compared to maven release plugin which
validates the release can be done (including tests) and runs the tests on
the tag as well
Now if 20
kip tests for the release
but it is at your own risk, can be fine or not - and "skip the deploy" -
here again you can configure maven to do it if you need but maven must
respect the build attached artifact.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
n. A lot of things ar imaginable.
>
> In future more lifecycles or workflows could be possible. For example a
> deploy
> lifecycle and so on. And then maven transform from a plugin execution
> framework
> to a process management framework, like Jason van Zyl described in his book
&g
weekend to all
> > . marco
> >
> > Sent from Outlook Mobile<https://aka.ms/blhgte>
> >
> >
> > From: Romain Manni-Bucau
> > Sent: Saturday, October 5, 2019 2:06:27 AM
> > To: Maven Developers List
> > Cc: users
+1 to switch it off by default (but keep the feature since it can help
investigations on CI)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://g
Le ven. 18 nov. 2022 à 09:39, Slawomir Jaranowski
a écrit :
> pt., 18 lis 2022 o 09:24 Romain Manni-Bucau
> napisał(a):
>
> > +1 to switch it off by default (but keep the feature since it can help
> > investigations on CI)
> >
>
>
> Text reports contain
Hi
For me it is:
* Tree: human work on transitivity
* List: pre-resolve for the runtime (dump jar list in a file)
* Resolve: CI init phase
Le jeu. 21 mars 2024 à 17:54, Christian Stein a écrit :
> I use the "resolve" goal like this:
>
> mvn --batch-mode --no-transfer-progress -DoutputFile=reso
