This has been driving me nuts. So wondering if anyone can spot why it’s happening. Here is an abridged version of my binary plugins: class MyBasePlugin implements Plugin<Project> { void apply(Project project) { project.apply plugin: MavenPublishPlugin project.publishing { …

Try something like project.getExtensions().configure(PublishingExtension, new ClosureBackedAction({ repositories.add(repo) }))

The issue doesn’t go away. I am still configuring the same extension even when I look it up by class, instead of name.

I cannot reproduce your problem with Gradle 2.4 and the information you provided. class MyBasePlugin implements Plugin<Project> { void apply(Project project) { project.apply plugin: MavenPublishPlugin project.publishing { repositories { maven{ name 'aRepo' } } } } } class LibraryPlugin …

That’s the frustrating part. I cannot reproduce it neither when I chuck everything in the same build.gradle file. It is only happening when they are spread out into their own classes in a binary plugin that I apply. There is literally nothing between when MavenPublishPlugin is applied and the first…

Are you sure you didn’t simplify too much your scenario ? Maybe there is a problem with the way you publish your plugins ? Beside these two points, there’s not much I can think of, except a Core Dev intervention :smile:

Here is the minimum build.gradle file that replicates the issue. Am I doing something really silly here? apply plugin: LibraryPlugin class MyBasePlugin implements Plugin<Project> { @Override void apply(Project project) { project.apply plugin: 'maven-publish' project.repositories { mav…

yes, there aren’t many differences indeed … I’m out of ideas… maybe you can add the --debug --stacktrace output to really pinpoint the problem. The difference between my working example and yours, concerning the project.publishing.repositories section, is that you define an url and some credenti…

[image] Sohrab_Hosseini: project.repositories { maven { url “${project.properties.mavenRepoUrl}/repo” } } For some insane reason, when I change that to url 'repo' in repositories, it starts working again. I am so confused!

Turns out it has to do with usage of project.properties which forces the project to be evaluated. Need to use project.property() instead. [image] Strange error in Publishing when using properties in Repositories Bugs I am consistently getting a strange error in publishing…

Configure publishing multiple times

Help/Discuss

Sohrab_Hosseini (Sohrab) May 28, 2015, 5:29am 10

Turns out it has to do with usage of project.properties which forces the project to be evaluated. Need to use project.property() instead.

Topic		Replies	Views
Configuring maven-publish publications in different plugins Help/Discuss	0	944	December 2, 2016
Apply maven-publish plugin from init script Old Forum Archive	12	9462	November 25, 2014
DeferredConfigurable evaluated too early Help/Discuss	1	480	April 1, 2017
Accessing project.properties before configuring 'publishing' extension causes a strange error Bugs plugins	0	2249	November 5, 2016
"Cannot configure the 'publishing' extension after it has been accessed." error since 4.8 Help/Discuss	6	1866	June 12, 2018

Configure publishing multiple times

Related topics