I've set
<parent>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>plugin</artifactId>
<version>1.551</version>
</parent>
And yes, I have 2 bouncy castle dependencies:
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk15on</artifactId>
<version>1.50</version>
</dependency>
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk15on</artifactId>
<version>1.50</version>
</dependency>
But I had them since I've started working on my plugin and build did
worked. Until today. All I did today was add another dependency to
<dependency>
<groupId>com.google.javascript</groupId>
<artifactId>closure-compiler</artifactId>
<version>v20140110</version>
</dependency>
and then when I tried to do a build again it didn't worked.
The weird thing is that i even reverted the code from GIT from before
adding the dependency to closure-compiler when builds did worked but to no
success i still wasn't able to do a build on that either.
On Tuesday, February 18, 2014 11:51:44 PM UTC+2, Jesse Glick wrote:
>
> BouncyCastle incompatibilities are a frequent headache for Jenkins
> plugin developers. Check the version of Jenkins core you are using,
> update as needed, and check your plugin’s declared dependencies:
> sshd-module? Anything which in turns depends on BouncyCastle?
>
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
