Project dependencies declared in .project files

Re:

Unrelated to Buildship: Generally you should avoid configuration time dependencies as much as possible and use artifacts instead. So if project A publishes some library and project B wants to consume it, then you would do something similar to this:

Yes, I am aware of that. Trying to avoid whenever possible - but it isn’t always possible. One of the big problems we are facing is this:

Other issue is that not every artifact is a single file. We need some to be directory structures. Making a file up would require packing that directory and unpacking it somehow every time it is used, which would be a performance suicide.

Unrelated but relevant note: I will be away for a month. Other people may communicate with you. I won’t post this to every discussion I started, though…