Open
Conversation
When the GRADLE_METADATA feature is enabled (e.g. by applying the 'cpp-application' plugin), a build fails to resolve the Node distribution as a dependency. This patch fixes this issue using explicitly specified metadata sources. See details: gradle/gradle#5008
Author
|
Just noticed that the But anyway these changes in Gradle's dependency management should be taken into account. Looks like a Node Maven repo mentioned here will be a good solution. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When Gradle 4.6 or higher is used and the
GRADLE_METADATAfeature is enabled (e.g. by applying thecpp-applicationplugin), a build fails to resolve the Node distribution as a dependency. This patch fixes this issue using explicitly specified metadata sources.See details: gradle/gradle#5008