node-gradle / node-gradle/gradle-node-plugin
download feature breaks settings repository
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 677
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
This plugin offers a functionality to download Node.js. If this functionality is used this plugin registers a new ivy repository for gradle.
This doesnt work very well if a user defines their repositories in settings.gradle.kts.
Depending on the value chosen for:
org.gradle.api.initialization.resolve.RepositoryMode
this will mean one of the following:
- PREFER_PROJECT: The registration of this Plugin will work, but gradle will drop previously working repositories defined in settings.gradle
- PREFER_SETTINGS: This registration of this Plugin will be ignored
- FAIL_ON_PROJECT_REPOS: The build will fail.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the Node.js download functionality and its Ivy repository registration, then compare it with repositories declared in settings.gradle.kts for each RepositoryMode. Define and test the intended behavior for PREFER_PROJECT, PREFER_SETTINGS, and FAIL_ON_PROJECT_REPOS; the issue is done when settings repositories are preserved and the build behavior is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, nodejs
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100