Just ran into the same issue... updating the <distributionManagement> section works. The Plugin Tutorial is outdated though:
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial links to https://github.com/jenkinsci/hello-world-plugin/blob/master/pom.xml#L34 (uses v2.2 of plugin parent) v2.2 of plugin parent still uses the old <distributionManagement>: https://github.com/jenkinsci/plugin-pom/blob/plugin-2.2/pom.xml#L761 It's probably best if the parent of hello-world-plugin would be updated to the latest plugin parent? Regards Georg On Thursday, 10 November 2016 16:39:34 UTC+1, Daniel Beck wrote: > > > > On 10.11.2016, at 08:12, Christian <[email protected] <javascript:>> > wrote: > > > > I tried setting a new parent, but then the build fails see > https://github.com/jenkinsci/claim-plugin/commit/56098d240dfedffd6f1fbc2426ac4724de0880f3#diff-0 > > > I tried locally with several different jenkins-test-harness.version but > it always fails with compilation errors, what am I doing wrong? > > > > I am currently not developing this plugin actively but thought I would > release a new version with some pull request from the community but the > release process is not as easy as one would like.. > > It seems like the dependency on mock_javamail needs to be explicit now. > Not sure where that's coming from. > > And since we moved from our forked and patched HtmlUnit to the upstream > one more than a year ago[1] to be able to support testing with modern > JavaScript frameworks, some methods and types have changed. The alternative > is stagnation and obsolescence. > > Additionally, the plugin used unsafe Jelly files, which could (with a > combination of other factors) result in XSS vulnerabilities. The HPI plugin > requires it to have an XML PI to escape by default for almost two years > now. > > This might look like a lot, but if the plugin has been stale for years, > even a single change per year can pile up. > > Note that the parent POM now by default runs FindBugs to improve code > quality, which results in a number of failures. You need to disable > FindBugs, or address these findings (fixing or ignoring). > > I've opened a pull request with all my changes. > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5814114f-1463-4d9e-b743-5050716699cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
