-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Cannot configure the 'publishing' extension after it has been accessed. #125
Comments
How do you hook up the publishing extension with the release? I don't see any dependsOn or anything like that. |
I didn't hook it up. Do I have to? I assumed there was no intrinsic dependency between them. |
The release plugin is not doing anything with the publish plugin. Are you sure the error appeared when you added the release plugin? |
I have the same issue, by just adding the plugin to the build.gradle file I got the same message "Cannot configure the 'publishing' extension after it has been accessed." |
Was it working with versions before 2.2? |
Ok as far as i can tell it is an issue with the order of plugins. Or at least this is a workaround to apply maven-publish after the release plugin. I will see if i can fix that. https://discuss.gradle.org/t/apply-maven-publish-plugin-from-init-script/2460 |
Ok I reproduced and fixed it in 4d31ad7. will be part of 2.2.1 |
correct, I just tried and release-plugin should be placed before maven-publish plugin |
Thanks a lot guys. |
People that run into "Cannot configure the 'publishing' extension after it has been accessed" google their way here, so I'll document an issue that had me going for quite a while.
is NOT the same as
The latter accessed the publishing Extension object which makes you run intor this issue. |
This is still an issue in gradle 4.5 with
then calling
and "fixed" by using |
build.gradle:
When running
./gradlew release
:And with debug and stacktrace on:
The text was updated successfully, but these errors were encountered: