I am trying to use both "update-parent" and "use-releases" goals to update
the version number in the parent section in the pom.xml file as well as the
versions in the dependency section so that it can resolve versions from
remote artifact repository such as Artifactory.
When executing either goal from the local computer, it can find newer
version from the local .m2 directory without problem.
When using "maven artifactory plugin" (2.9.1) together with
versions-maven-plugin (2.3) on Jenkins server, "version-maven-plugin" was
not able to consult remote repositories. It could be because
"versions-maven-plugin" is not aware of the remote repositories configured
for "artifactory maven plugin" but I am not entirely sure.
The following is the Jenkins pipeline script to use artifactory plugin and
set up with resolver:
rtMaven = Artifactory.newMavenBuild()
rtMaven.resolver server: server, releaseRepo: 'xxx-release-virtual',
snapshotRepo: 'xxx-snapshot-virtual'
rtMaven.run pom: 'pom.xml', goals: 'versions:update-parent
-DparentVersion=[0.0.2]'
I can verify that version exists on artifactory's virtual repository.
The current only way "versions-maven-plugin" is able to find the version is
to have that version installed on the Jenkins server's .m2 directory.
Where can I find more information about how to configure remote
repositories for "versions-maven-plugin" ?
Thank you.
--
You received this message because you are subscribed to the Google Groups
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/mojohaus-dev/031bbc4e-d603-4e1c-a99f-895bde13381c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
