One of the things that we do quite a bit is browse the project for a file, so that any file references when we deploy are all relative. And I found your example that mentions the @EclipseWorkspacePath annotation in the Browsing section of the Sapphire Help, which is great if you're dealing with Workspace-relative paths, but not specific enough for Project-relative paths.
That led me to poke around with creating a custom class extending BasePathsProviderImpl... but then I stumbled upon ProjectRootBasePathsProvider.
Is there a reason this is internal? I know I could simply make a copy of the class and stash it in my own project, but that kind of defeats the purpose.
Should I report an enhancement request to change the visibility of that class?