-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins v 1.480.3
In a maven job, inside "Invoke top-level Maven targets" it always have the option "use private maven repository" checked by default. When I uncheck it, save the configuration and then go back into the job configuration it is checked again.
I was able to workaround this by going to "Manage Jenkins -> Configure System -> Maven Project Configuration" and setting "Local Maven Repository" to 'default'.
Looking at the jenkinsci-dev mailing list looks like user Jorg Heymans discovered this problem in version 1.466.1 [1]
And I was able to discover the previously mentioned workaround from hints from stackoverflow [2]
Thanks.
[1]: https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/%22use$20private$20maven$20repository%22/jenkinsci-dev/QqP4wl6fack/5FX4bw6O1aoJ
[2]: http://stackoverflow.com/questions/11756528/jenkins-disable-or-clear-cache-for-maven-builds
Is it reproduced with a recent version of the Maven plugin?