That's good to know Robert, thank you
I will add that to our release dryrun and hopefully it will catch more of
the uncaught problems early on
Alejandro Endo | Software Designer/Concepteur de logiciels
From: "Robert Scholte"
To: "Maven Users List" ,
Date: 2014-11-28 12:46 PM
Subj
But the problem has nothing to do with Jenkins
You can manually type mvn release:prepare release:perform -DdryRun=true
and it will pass and then dryRun=false and it will fail
My point is about the default behaviour of a dry run not being realistic
compared to a full release, which will make you
O wait a sec you're using the evil job type...
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html
Well all bets are off then that will most likely royally screw you over
On 28 November 2014 at 17:45, Robert Scholte wrote:
> Op Fri, 28 Nov 2014 00:5
Op Fri, 28 Nov 2014 00:54:29 +0100 schreef
:
I'm using the release-plugin v2.5.1 and I'm often encountering two
recurring stories with failed releases
1) Now the release can fail due to errors in the javadoc. This is not a
problem, the problem is that IF there are problems in the javadoc the
Op Thu, 27 Nov 2014 14:12:58 +0100 schreef Dutz, Christofer
:
Hi,
I just ran into a problem I was having a few times now with the release
plugin. This time the usage scenario is different, but the code needed
to be changed is still the same.
This time I am helping migrate a large set of
Hi Stephen,
We are not using any preparationGoals. So it's not that my preparation
goals are not mimicking a full release. It is that the default dry run is
not mimicking a default full release.
We are talking about completely vanilla release:prepare. The only
non-default value is the resume=f
