multi-project + retrieveManaged => bad classpath

[ghost]

http://stackoverflow.com/questions/21315555/configuring-sbteclipse-to-get-the-right-value-for-lib-managed

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.

[er1c]

Can you supply a sample project/issue for this?

[jnfeinstein]

Confirmed, this is definitely a thing. Looks like any root container project with real subprojects should experience this issue.

EDIT: Doesn't look like this project (sbteclipse) has the issue. I thought it might be something scala vs java, but I do in fact have a scala project that is displaying this issue.