> On 10.11.2016, at 08:12, Christian <[email protected]> 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/4818CB7C-5371-4531-A49D-E8739FD38758%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
