How to override the plugin version seen by plugin manager area

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

How to override the plugin version seen by plugin manager area

Michael Carter
Hopefully a quick question with a quick answer.

I have this in my pom.xml to override the file name:

        <finalName>${project.artifactId}-${project.version}-${timestamp}</finalName>

How do I get the ${timestamp} added to the version that the plugin manager sees?  I'm assuming it's the Implementation-Version and/or Plugin-Version in the MANIFEST.MF but can't seem to figure out how to manipulate it in the pom.xml

Thanks,
Michael

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/24a5e7be-7021-4007-8c60-60f8920d4c97o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: How to override the plugin version seen by plugin manager area

Jesse Glick-4
On Tue, Jul 14, 2020 at 11:25 AM Michael Carter
<[hidden email]> wrote:
> Hopefully a quick question with a quick answer.

Quick answer: you cannot.

Long answer: replace `maven-release-plugin` with something based on
Maven “CI-friendly” versions. Would not recommend it unless there is a
compelling need.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3TZGiFUeG-RosEjFQYTE06F%2BijJzm5ZNjge70K_M22EA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: How to override the plugin version seen by plugin manager area

Daniel Beck


> On 14. Jul 2020, at 18:39, Jesse Glick <[hidden email]> wrote:
>
> Would not recommend it unless there is a
> compelling need.

Recent releases of Jenkins also show release dates in the plugin manager, the release dates are shown on the plugins site and in tooltips on the archives page, so I would be surprised if there is such a need while following our recommended practices.

I also wouldn't be surprised if this behavior breaks some parts of our automation.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D4CA2D97-9DCC-4979-B4DD-3212EBF1E491%40beckweb.net.