Despite the fact that the plugin is configured with the snapshot update policy = always (as shown in the attached screenshot), it always uses the snapshot version that is already available on the local Maven repository of the Jenkins slave.
I consider this bug as a Major one as it is not possible to leverage this plugin to auto-deploy overnight the latest SNAPSHOT version
|Field||Original Value||New Value|
|Assignee||Robert Kleinschmager [ barclay_reg ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Workflow||JNJira [ 151787 ]||JNJira + In-Review [ 194094 ]|