Skip to content
Permalink
Browse files

[INFRA-588] Overwrite distribution management

  • Loading branch information
vjuranek committed Oct 19, 2016
1 parent 29224df commit 874a2812504e0a1e3e9753feca85018767ee84ab
Showing with 7 additions and 0 deletions.
  1. +7 −0 pom.xml
@@ -66,6 +66,13 @@
</plugins>
</build>

<distributionManagement>
<repository>
<id>repo.jenkins-ci.org</id>
<url>https://repo.jenkins-ci.org/releases</url>
</repository>
</distributionManagement>

<repositories>
<repository>
<id>repo.jenkins-ci.org</id>

6 comments on commit 874a281

@daniel-beck

This comment has been minimized.

Copy link
Member

@daniel-beck daniel-beck replied Oct 19, 2016

@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.

@vjuranek

This comment has been minimized.

Copy link
Member Author

@vjuranek vjuranek replied Oct 19, 2016

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...

@daniel-beck

This comment has been minimized.

Copy link
Member

@daniel-beck daniel-beck replied Oct 19, 2016

@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.

@vjuranek

This comment has been minimized.

Copy link
Member Author

@vjuranek vjuranek replied Oct 19, 2016

@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:-))

@daniel-beck

This comment has been minimized.

Copy link
Member

@daniel-beck daniel-beck replied Oct 19, 2016

@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

@vjuranek

This comment has been minimized.

Copy link
Member Author

@vjuranek vjuranek replied Oct 19, 2016

@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

Please sign in to comment.
You can’t perform that action at this time.