Thanks stephen. And as Baptiste pointed out (on irc) this pattern is used in the 1.10.x lineage of pipeline plugins (https://github.com/jenkinsci/pipeline-plugin/tree/1.10.x).
I just did a push again with the <url> elements, and will see tomorrow (my time) if things land correctly in the experimental update centre and report back. Thanks! On Monday, July 4, 2016 at 7:34:29 PM UTC+10, Stephen Connolly wrote: > > The check for a <url> in the pom does not take into account inheritance > from the parent. This is perhaps deliberate, but the check certainly could > be refined for these multi-module releases... > > On the other hand the <url> property is one of the "magic" ones whereby if > unspecified it is the parent url plus the artifactId (depending on whether > the parent url has or doesn't have a trailin / or some other silly > convention) so perhaps it is best to force the "must override" rule > > On 4 July 2016 at 03:45, Michael Neale <mne...@cloudbees.com <javascript:> > > wrote: > >> Need some help from someone experienced in deploying new plugins. >> >> Last week a release was performed on blue ocean, to get it to the >> experimental update center, but it hasn't shown up. >> >> Blue ocean is a multi module project, with a few plugins, so this is a >> bit unfamiliar to most (pipeline was originally deployed this way). >> >> Following the guide as per >> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins, there is a >> wiki https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin page >> setup in the pom.xml. >> >> The plugins show up in the repo: >> http://repo.jenkins-ci.org/public/io/jenkins/blueocean/ >> but not in the update center: >> http://updates.jenkins-ci.org/experimental/update-center.json >> >> >> >> Perhaps given the plugin that people will in stall is the "aggregator" - >> should the <url> to the wiki page be in the blueocean-plugin submodule >> instead of on the parent? >> >> >> >> Any reviews/tips appreciated: >> https://github.com/jenkinsci/blueocean-plugin >> >> The link at the bottom >> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins points to a >> non existent job that has the update center build log, so it isn't easy to >> see if something is going wrong. >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-de...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/b52ccf97-edfa-46c5-94e9-82f5770f70dd%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/b52ccf97-edfa-46c5-94e9-82f5770f70dd%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/944106eb-063d-45fe-84ee-d1a4d00b1fe3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
