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

Find a way to detect version conflict #10

Open
lacasseio opened this issue Nov 16, 2020 · 2 comments
Open

Find a way to detect version conflict #10

lacasseio opened this issue Nov 16, 2020 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@lacasseio
Copy link
Member

When using the following in a buildSrc project:

dependencies {
    implementation platform("dev.nokee:nokee-gradle-plugins:0.5.0-fcde9b9d")
}

and the Nokee init project on another version, it wrongly mentions the Nokee version loaded at all Nokee plugins are available on the classpath via the platform from buildSrc. We should have a pill in the classpath to find the Nokee version (and versions, if misaligned) to give a better error message or warning.

@lacasseio lacasseio added the bug Something isn't working label Nov 16, 2020
@lacasseio
Copy link
Member Author

For example, build dependencies are:
Screen Shot 2020-11-16 at 1 16 20 PM

But console shows:
Screen Shot 2020-11-16 at 1 19 25 PM

@lacasseio lacasseio added this to the 0.8.0 milestone Feb 10, 2021
@lacasseio
Copy link
Member Author

For version 0.8.0 we expanded and improved the version detection and also detect the right version used. All we are missing for this story is more testing around what is printed when a version is conflicted.

@lacasseio lacasseio modified the milestones: 0.8.0, 0.9.0 Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant