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

Fix dependency versioning #12

Merged
merged 2 commits into from
Jun 29, 2022
Merged

Fix dependency versioning #12

merged 2 commits into from
Jun 29, 2022

Conversation

rwjc
Copy link
Contributor

@rwjc rwjc commented Jun 29, 2022

There was a problem with publishing after merging #11.

(We really should have an action to check build before merging)

The dependencies were set up to use a version that does not exist in any repo.

  • plunge-gradle-plugin/build.gradle: change to depend on the local project instead
  • sample/build.gradle: change to depend on the latest version that exists on maven central, which itself has a dependency on 1.0.0 of nz.co.trademe.plunge:plunge-parsing (this at the moment only exists on jcenter).

Rick Chen added 2 commits June 29, 2022 19:57
Can't use version that hasn't been published yet.

This is further complicated by current 1.0.1 version on MavenCentral [1]
has a dependency on 1.0.0 of `nz.co.trademe.plunge:plunge-parsing` which
only existed in jcenter.

Once we've bootstrapped a new version of that into MavenCentral then we
can get rid of the jcenter repo.

[1] https://search.maven.org/artifact/nz.co.trademe.plunge/plunge-gradle-plugin/1.0.1/jar
@rwjc rwjc merged commit 79bf821 into master Jun 29, 2022
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

Successfully merging this pull request may close these issues.

1 participant