blocks|key|6032|text|问题是，当我将不同的部分添加到兄弟项目中时，这意味着我有两个项目定义了buildscript+{}部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6033|buildscript+{
++++...
++++dependencies+{
++++++++classpath+group:'org.jfrog.buildinfo',+name:+'build-info-extractor-gradle',+version:+'3.0.1'
++++}
}|code-block|syntax|javascript|6034|显然，这导致类路径中存在两个不同版本的依赖项，因此出现错误。|6035|解决方案是将buildscript位移动到主项目中，以便这些依赖项只定义一次：|6036|buildscript+{
++++repositories+{
++++++++maven+{+url+"https://plugins.gradle.org/m2/"+}
++++}
++++dependencies+{
++++++++classpath+group:'org.jfrog.buildinfo',+name:+'build-info-extractor-gradle',+version:+'3.0.1'
++++}
}|6037|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The problem was that when I added the various bits to the sibling project that meant I had two projects defining the buildscript {} section. 

<pre><code>buildscript {
 ...
 dependencies {
 classpath group:'org.jfrog.buildinfo', name: 'build-info-extractor-gradle', version: '3.0.1'
 }
}
</code></pre>

Apparently that caused two different versions of the dependency to exist in the classpath, hence the error.

The solution was to move the buildscript bit into the master project so those dependencies are only defined once:

<pre><code>buildscript {
 repositories {
 maven { url "https://plugins.gradle.org/m2/" }
 }
 dependencies {
 classpath group:'org.jfrog.buildinfo', name: 'build-info-extractor-gradle', version: '3.0.1'
 }
}
</code></pre>

blocks|key|4513447|text|为了防止它对某些人有帮助，我得到了相同的错误，但原因不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4513448|我的build.gradle中有以下内容|offset|length|style|CODE|4513449|dependencies+{
++++classpath+"org.jfrog.buildinfo:build-info-extractor-gradle:%2B"
}|code-block|syntax|javascript|4513450|在构建过程中，artifactory插件将自身从版本3.x更新到版本4.x，因为没有为依赖项指定特定的版本。在它更新之后，我得到了错误(Could+not+find+any+convention+object+of+type+ArtifactoryPluginConvention)。|4513451|我猜问题是我的构建脚本中的其余配置不能与新的插件版本一起工作。将依赖项设置为使用3.x版本为我解决了这个问题：|4513452|dependencies+{
++++classpath+"org.jfrog.buildinfo:build-info-extractor-gradle:3.%2B"
}|4513453|entityMap^0|0|2|C|0|0|1W|20|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|13|8|@]|9|@]|A|$K|L]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

In case it helps someone, I got the same error, but for a different reason.

I had the following in my <code>build.gradle</code>:

<pre><code>dependencies {
 classpath "org.jfrog.buildinfo:build-info-extractor-gradle:+"
}
</code></pre>

At some point the artifactory plugin updated itself from version 3.x to version 4.x while building, because no specific version was specified for the dependency. After it updated I got the error (<code>Could not find any convention object of type ArtifactoryPluginConvention</code>).

I guess the problem was that the rest of the configuration in my build script doesn't work with the new plugin version. Setting the dependency to use version 3.x fixed the problem for me:

<pre><code>dependencies {
 classpath "org.jfrog.buildinfo:build-info-extractor-gradle:3.+"
}
</code></pre>

blocks|key|6129|text|在使用Jenkins进行构建时，我遇到了类似的异常。对我来说，冲突的是Jenkin的版本和构建脚本中的版本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6130|​|6131|📷|atomic|offset|length|6132|6133|为了解决这个问题，构建的Artifactory部分有一个标记，您可以选中指定要使用gradle文件中的版本：|6134|6135|6136|6137|这解决了我的问题。希望能有所帮助。|6138|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/8f5aee23c6b08f31f22d05f553bc7730.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/088421bf78574f898b2fe3e25e03c8b9.png^0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|13|8|@]|9|@$G|14|H|15|1|16]]|A|$]]|$1|I|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|M|3|E|5|F|7|1A|8|@]|9|@$G|1B|H|1C|1|1D]]|A|$]]|$1|N|3|C|5|6|7|1E|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]|Z|$5|T|U|V|A|$W|10|Y|-4]]]]

I was getting a similar exception when building with Jenkins. For me the conflict was with Jenkin's version and the version in the Build script:

<a href="https://i.stack.imgur.com/vn4UV.png" rel="noreferrer"><img src="https://i.stack.imgur.com/vn4UV.png" alt="Jenkins Build Error"></a>

To address this the Artifactory section of the build has a flag you can check specifying that you want to use the version from the gradle file:

<a href="https://i.stack.imgur.com/bodSD.png" rel="noreferrer"><img src="https://i.stack.imgur.com/bodSD.png" alt="Flag to fix issue"></a>

This fixed my issue. Hope it helps.

blocks|key|6200|text|这是另一个潜在的原因。所有这一切看起来都是定义类的竞争类加载器的问题。完全限定的类包括加载器。因此，load+A+foo.bar不是loader+B+foo.bar，跨越这一界限是需要接口和仔细定义的复杂舞蹈。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6201|因此，当使用Jenkins+artifactory插件构建gradle项目时，您必须添加usesPlugin，否则jenkins插件将生成一个初始化脚本，该脚本将gradle插件添加到类加载器中。|6202|def+server+=+Artifactory.server+"artifactory"
def+rtGradle+=+Artifactory.newGradleBuild()
rtGradle.usesPlugin+=+true+//+Artifactory+plugin+already+defined+in+build+script
...|code-block|syntax|javascript|6203|我的问题是，桌面构建正常，jenkins构建显示了这篇文章的问题|6204|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Here's another potential cause. All of this looks to be a problem with rival classloaders defining the class. The full qualified classes include the loader. so, load A foo.bar is not loader B foo.bar and crossing that divide is a complex dance requiring interfaces and careful definition.

So, when using the Jenkins artifactory plugin to build your gradle project with the gradle artifactory plugin, you must add the usesPlugin or jenkins plugin will generate an init script which adds the gradle plugin on to a class loader.

<pre><code>def server = Artifactory.server "artifactory"
def rtGradle = Artifactory.newGradleBuild()
rtGradle.usesPlugin = true // Artifactory plugin already defined in build script
...
</code></pre>

My problem was, desktop build OK, jenkins build shows this post's problem

blocks|key|6254|text|我得到了竹子抛出的同样的异常：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6255|'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention@18eb2827'+with+class+'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'+to+class+'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'|code-block|syntax|javascript|6256|由于竹子竹子工厂插件默认在每个子项目模块中查找gradle.propeties文件，因此必须在那里提供该文件。|6257|不需要在build.gradle文件中发布逻辑，因为竹子工匠插件将分别读取每个模块的gradle.properties文件，其中包括：|6258|group=com.example
artifactId=your-project
version=1.0.0|6259|我抛出ArtifactoryPluginConvention异常的原因是我在竹子上配置的构建计划配置错误。|6260|由于配置错误，任务的构建顺序不正确。看看你的竹子构建任务/最好克隆一个已经在工作的竹子计划。|6261|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I got the same exception thrown by bamboo:
<pre><code>'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention@18eb2827' with class 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention' to class 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'
</code></pre>
Since the bamboo Bamboo Artifactory Plugin by default looks for the gradle.propeties file in each sub-project module, it has to be provided there.
There is no need for publishing logic in the build.gradle file since the Bamboo Artifactory plugin will read the gradle.properties file for each module respectively, containing:
<pre><code>group=com.example
artifactId=your-project
version=1.0.0
</code></pre>
The reason that I got the ArtifactoryPluginConvention exception thrown was that my configured build plan on Bamboo was misconfigured.
With misconfigured, the build ordered of the tasks was not correct. Have a look at your bamboo building tasks/preferably clone a Bamboo plan that is already working.

Here's the configuration to get the artifactory plugin:

<pre><code>buildscript {
 repositories {
 mavenCentral()
 maven { url 'http://jcenter.bintray.com' }
 }
 dependencies {
 classpath group:'org.jfrog.buildinfo', name: 'build-info-extractor-gradle', version: '3.0.1'
 }
}
apply plugin:'com.jfrog.artifactory'
apply plugin:'ivy-publish'

...some publish spec stuff...
</code></pre>

I run gradle (2.3) and I get:

<pre><code>&gt; Failed to apply plugin [id 'com.jfrog.artifactory']
 &gt; Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention@6b6c7be4' with class 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention' to class 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'
</code></pre>

Certainly looks like a classpath issue, but I literally have this project and a sibling project using this same set of gradle/artifactory configurations and one works and the other does not. Both are part of the same top level project. Same JDK (1.8.0_20). Same Gradle. Same everything.

I'm baffled...

Gradle artifactory plugin saying "Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'..."

下面是获取artifactory插件的配置：buildscript {    repositories {        mavenCentral()        maven { url 'http://jcenter.bintray.com' }    }    dependencies {        clas...

问Gradle artifactory插件显示"Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'...“
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle artifactory插件显示"Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'...“EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gradle artifactory插件显示"Cannot cast object 'org.jfrog.gradle.plugin.artifactory.dsl.ArtifactoryPluginConvention'...“
EN