... and that did the trick:
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>11.0.1</version>
<scope>test</scope>
</dependency>
Output:
62.511 [jobname-PipelineManualFailTest #1] [Pipeline] node
62.763 [jobname-PipelineManualFailTest #1] Running on Jenkins in
....workspace/jobname
62.964 [jobname-PipelineManualFailTest #1] [Pipeline] {
63.568 [jobname-PipelineManualFailTest #1] [Pipeline] stage
63.668 [jobname-PipelineManualFailTest #1] [Pipeline] { (Example Build)
64.121 [jobname-PipelineManualFailTest #1] [Pipeline] sh
Guess that's what had me all turned around when I saw the guava jar coming
from the jenkins-core I just assumed it was the correct one I should be
using.
Thanks for all the help everyone!
On Wednesday, July 15, 2020 at 2:05:15 PM UTC-4, Michael Carter wrote:
>
> +- org.jenkins-ci.main:jenkins-core:jar:2.235.1:provided
> | +- com.google.guava:guava:jar:27.1-jre:provided
>
> Guess that's my problem... somehow when I upgraded the pom.xml to pull the
> 2.235.1/2.222.4 it must have broke then.
>
> At least this gives me a place to start looking.
>
> On Wednesday, July 15, 2020 at 1:42:56 PM UTC-4, Jesse Glick wrote:
>>
>> On Wed, Jul 15, 2020 at 9:17 AM Michael Carter
>> <[email protected]> wrote:
>> > so it can pick up version 27.1-jre of guava from the war.
>>
>> From `jenkins.war`? As mentioned, that bundles 11, not 27. Keep
>> editing `pom.xml` until
>>
>> $ mvn dependency:tree | fgrep guava
>> [INFO] | +- com.google.guava:guava:jar:11.0.1:provided
>>
>> > problem is backtracking what I added from it last working is near
>> impossible at this point.
>>
>> git bisect
>>
>
--
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/c2bc8121-ae41-404c-98f0-3c4f67171877o%40googlegroups.com.
