nebula-plugins / nebula-plugins/nebula-release-plugin
BUG: Interferes with Dependency Resolution When Branch Name Contains Double Hyphen
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
./gradlew clean
FAILURE: Build failed with an exception.
- What went wrong:
A problem occurred configuring project ':account-inquiry-starter'.
Could not determine the dependencies of null.
Could not resolve all dependencies for configuration ':account-inquiry-starter:classpath'.
> Identifiers MUST NOT be empty
git branch -M test--branch./gradlew clean- error from abovegit branch -M test-branch./gradlew clean- success
Oddly, the bug does not happen if I do: ./gradlew clean snapshot
Contributor guide
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
Reproduce the failure by renaming the branch to test--branch and running ./gradlew clean, then compare it with test-branch and with ./gradlew clean snapshot. Trace the Gradle dependency-resolution path involved in the reported “Identifiers MUST NOT be empty” error; done means ./gradlew clean succeeds with a branch name containing a double hyphen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100