@vjuranek Consider using the 2.x parent POMs (2.4 or higher for this issue) that let you independently define the Jenkins version you're compatible with instead.

thanks @daniel-beck it's on my todo list - I wanted to test it carefully if updating to 2.x parent can break something, so based on this comment I guess there aren't any known issues...

@vjuranek If so, shouldn't be too severe given the number of plugins doing that already. if you find something, please file and feel free to ping me.

@daniel-beck sure, I'll rise an issue if I run into some problems (I also don't expect any issues as I haven't seen any complains, but I just didn't want to blindly apply some changes, as I'm not very familiar with 2.X changes in the core (another item on my todo list:-))

@vjuranek

2.X changes in the core

Please note that the 2.x plugins POM has been made independent of the Jenkins version dependency. So you can keep the 1.580 dependency on core while getting the 2.x plugins POM goodness.

See https://github.com/jenkinsci/plugin-pom and https://github.com/jenkinsci/maven-hpi-plugin/blob/master/hpi-archetype/pom.xml

@daniel-beck yes, I'm aware I can use 2.X parent pom while stick with 1.X Jenkins core via setting up <jenkins.version>, I used bad wording, I meant I needs to become more familiar with all the 2.X changes, including POM restructure