multi-project + retrieveManaged => bad classpath
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 712
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Description
The above post describes a bug I encountered.
Originally I had the following directory structure. 'A' and 'B' are sub-projects that make up my multi-project named 'project'. 'ws' is my eclispe workspace.
/home/ws/project/A
/home/ws/project/B
projects 'A' and 'B' would reference classpath dependencies with the following path structure "../lib_managed" which in practice resolved to "/home/ws/../lib_managed"
As a work-around, I was able to create another ws,
/home/ws1
and created the following symlink,
/home/project => /home/ws/project
which by-passed the bad classpath dependency references.
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
Start with the linked Stack Overflow report and reproduce the multi-project layout using sub-projects A and B. Inspect how retrieveManaged produces classpath dependency paths; done means the generated paths resolve correctly without the workspace symlink workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100