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
CNFE with Gradle > 1.9 #24
Comments
Although 0.5-beta-1 is supposed to have been released to fix this, there is no sign of the release anywhere in maven repositories on github or elsewhere. |
This looks like a duplicate of #16 to me. Have you tried adding the github repository to your build script repositories as it is described in the readme? |
Actually I added it to my nexus repository. But you are right... I see it here: https://github.com/ben-manes/gradle-versions-plugin/tree/mvnrepo/com/github/ben-manes/gradle-versions-plugin/0.5-beta-1 Must be my config somewhere... please close. |
@aalmiray please try with 0.5-beta-1 and report back if that doesn't fix your issue. |
I see why... your maven "repository" is missing all the index files. You may wish to investigate https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide for publishing your artifacts. I use it for my own open source projects and it is really easy once you have it set up. |
The github repository is just a temporary workaround until 0.5 is released, which - unfortunately - I cannot do because I am not the project owner and have just stepped in. Please don't ask me for an ETA though, I wouldn't know. |
Oh, ok. Sonatype are happy to accept betas... Anyhow, I've gone and forked this for my own use and uploaded it to a private repository. All looking good. Thanks. |
I suggest you to consider publishing binaries to Bintray (as noted in #23). The advantage is that you can push as many types of binaries (beta, alpha, snapshot, final, etc) as a developer you're in charge of what you push. There's also an option to link your binaries to JCenter and Maven Central. |
The following exception appears with version 0.4 of the plugin in combination with Gradle 1.10 and 1.11
The text was updated successfully, but these errors were encountered: