You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
thank you @dantran , i assume this trick will work.
i tried to stay simple, i preferred not touching the rpm version, letting the plugin do the job.
In them Maven pom.xml I define 6.1.6-SNAPSHOT and the CI (Jenkins) replace the SNAPSHOT with version 1,2,3... only on builds that are marked for release (the _1 is added by the plugin). for now, i don't want to touch this mechanism.
In the meantime, i will use the downgrade method in yum: yum downgrade myProject-6.1.6-SNAPSHOT20190430221146
Here is my issue with SNAPSHOT using Git+Maven+RPM during development.
myProject
version 6.1.6 release 2_1 and 3_1.yum update
.<version>6.1.6-3</version>
assuming i need to fix a bug in version 3_1:
<version>6.1.6-SNAPSHOT</version>
What am i missing?
maybe the plugin use
epoch
for SNAPSHOT builds?here is example of my yum repo:
The text was updated successfully, but these errors were encountered: