Skip to content
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

Failed upgrading from 0.19.1 to 0.20.0 #433

Open
adil-hussain-84 opened this issue Jun 11, 2020 · 3 comments
Open

Failed upgrading from 0.19.1 to 0.20.0 #433

adil-hussain-84 opened this issue Jun 11, 2020 · 3 comments

Comments

@adil-hussain-84
Copy link

I just tried upgrading from version 0.19.1 of the plugin to version 0.20.0 and I'm seeing the following error when Gradle attempts to configure the project:

A problem occurred configuring root project 'some-project'.
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find any version that matches org.pegdown:pegdown:1.6.+.
     Versions that do not match:
       - 1.5.0
       - 1.4.2
       - 1.4.2-atlassian-1
       - 1.4.1
       - 1.4.0
       - + 10 more
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/pegdown/pegdown/maven-metadata.xml
       - https://jcenter.bintray.com/org/pegdown/pegdown/maven-metadata.xml
       - https://plugins.gradle.org/m2/org/pegdown/pegdown/maven-metadata.xml
     Required by:
         project : > gradle.plugin.org.openbakery:plugin:0.20.0

I have tried declaring the plugin with both the plugins { id "org.openbakery.xcode-plugin" version "0.20.0" } notation and the dependencies { classpath "gradle.plugin.org.openbakery:plugin:0.20.0" } } notation and the result is the same both times.

@renep
Copy link
Contributor

renep commented Jun 12, 2020

Pegdown is the problem and I want to get rid of it see: #431

For a workaround see: #430 (comment)

@adil-hussain-84
Copy link
Author

adil-hussain-84 commented Jul 9, 2020

Thanks for the response @renep. It looks like all I was missing was a mavenCentral() build script repository declaration. I had jcenter() and not mavenCentral(). Looks like the org.pegdown:pegdown:1.6.+ artifact exists in Maven Central but not in JCenter.

@renep
Copy link
Contributor

renep commented Jul 10, 2020

I already have remove pegdown in the develop branch, because I was used in the HockeyKit part that I have also ditched and a ReleaseNotes tasks, that I have added a very long time ago, but have never really used is. So it's gone too. 😬

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants