useProjectID does not work in multi-project settings
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 712
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Description
lazy val a = project.in( file("a" ).settings( name := "project-a" ).settings( EclipseKeys.useProjectId := true )
lazy val b = project.in( file("b") ).dependsOn(a)
after running eclipse, eclipse project name for a is indeed a, however, in .classpath of b, name of the dependent project from a is project-a not a
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
Reproduce the issue with the multi-project definition in the report, enabling EclipseKeys.useProjectId for project a and running eclipse. Inspect b's generated .classpath; the fix is complete when its dependency refers to Eclipse project a rather than project-a.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100