use a versionthat works give prior releases

[jtnord]

400.v12312312 is older than 1.1 in Maven but not jenkins. this confuses tools that use maven for version comparison, most likely dependabot et al).

@jglick @Pldi23

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jtnord]

jenkinsci/incrementals-tools#19 (comment)

[daniel-beck]

dependabot

Dependabot seems to handle it well: jenkinsci/jenkins#6159

[jglick]

I suspect just updating the extension to 1.3 should suffice.

[jtnord]

dependabot

Dependabot seems to handle it well: jenkinsci/jenkins#6159

me goes off to file an issue against dependabot

[jtnord]

I suspect just updating the extension to 1.3 should suffice.

how would that help? it will still produce versions like nnn.vxxxxxxxxx the problem is maven treats the entire version as a string if a dotted part is not parsable as an integer?

[jtnord]

sorry for the noise - I ran the comparison inside Jenkins in the script console. When I use Maven libraries directly from maven 3 (3.8.4) maven does sort the version as newer, older versions of maven (2.x) sort as originally described.

[jglick]

I filed jenkinsci/incrementals-tools#29 to track investigation.