Why does the plugin parent point to an old core version?

[Marc Rohlfs]

Hi,

maybe an obsolete question, but I didn't find any regarding information:

For plugin development, https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites encourages you to aggregate org.jenkins-ci.plugins:plugin as parent POM. AFAIK this denotes the "Minimum Jenkins requirement" in the plugin doc. I noticed, that all new versions (2.*) define dependencies to the Jenkins core version 1.625.3. But I'd rather expect them to the core version, that matches the org.jenkins-ci.plugins:plugin version - as I'd rather like to write my plugin against new/current API versions. Did I miss something?

Kind regards

Marc

[Jesse Glick]

On Tue, Jun 6, 2017 at 1:04 PM, 'Marc Rohlfs' via Jenkins Developers
<jenkin...@googlegroups.com> wrote:
> Did I miss something?

Yes. Override the `jenkins.version` property to whatever you like. See

https://github.com/jenkinsci/plugin-pom#introduction

(Generally speaking, wiki content is old and unreliable.)

[Marc Rohlfs]

Many thanks! Didn't check that page. I've been away from Jenkins plugin development for two years and actually don't know where "the places to look" are - if it's not the wiki ...