We could include them, so that they get correctly resolved. The thing is
that given the JTH version is configurable, some coordination between some
versions would be needed (maybe using profiles)...
Of course, this would be a transient situation for older plugins in the new
parent pom but we should
In my case is has been caused by the outdated dependency in parent pom (2.6)
[INFO] org.jenkins-ci.plugins:promoted-builds:hpi:2.26-SNAPSHOT
[INFO] +- org.jenkins-ci.main:maven-plugin:jar:2.0:compile
[INFO] | +- org.apache.httpcomponents:httpcore:jar:4.2.4:compile
httpcore 4.3+ is required to ma
On Mon, Mar 7, 2016 at 5:44 PM, Andres Rodriguez
wrote:
> You should look in your dependency tree for conflicting dependencies and
> resolve them.
Example:
https://github.com/jenkinsci/pipeline-stage-view-plugin/commit/c83c436aee00f1b02922cfa346f2ad33b3b044a3
--
You received this message becau
Hi Tomas,
The parent pom 2.3 uses by default the split JTH 2.1, which uses HtmlUnit
2.18 which depends on org.apache.httpcomponents:httpclient:jar:4.5.
You should look in your dependency tree for conflicting dependencies and
resolve them.
If you post the result of `mvn dependency:tree` I can try
I'm getting an error when trying to use the new plugin parent 2.3.
The PR with the
change: https://github.com/jenkinsci/violation-comments-to-github-plugin/pull/1
And the log from that
build:
https://jenkins.ci.cloudbees.com/job/plugins/job/violation-comments-to-github-plugin/16/console
Apache
