Hello,
On 15 October 2015 at 10:52, Greene, Hugh [email protected] wrote:
I don’t have a full solution for you, just a clue. I had a similar
confusing error using an in-house Gradle plugin with a multi-project
build, under Gradle 1.4. The underlying cause was that, if a plugin is
applied in multiple subprojects but not in their parent project
(usually the root project) Gradle seems to load the plugins for each
project into a separate classloader. That gives you class cast
exceptions when the plugin instance on one project tries to use
objects from the plugin on another project. The “fix” was to apply the
plugin in the root project as well, even though it wasn’t used there.
Thanks for your suggestion! I added this to the root project:
buildscript {
repositories {
maven {
url "https://plugins.gradle.org/m2/";
}
}
dependencies {
classpath "org.jfrog.buildinfo:build-info-extractor-gradle:3.1.1"
}
}
And it seems to be working now. The funny thing is that I cannot
actually apply the Artifactory plugin to the root project or it fails
too, I can only declare the class path. To be honest it seems like a
bug in the plugin somewhere, given that the protobuf plugin has no
such shortcomings.
Cheers,
--
Qnective
Alex Silva
Software Engineer
Thurgauerstrasse 54 | 8050 Zürich | Switzerland
http://www.qnective.com/ | [email protected]
------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
