How to create ILocation?

Just as future reference the code needed is mentioned in https://jazz.net/forum/questions/158130/how-to-programmatically-construct-the-absolute-uri-for-an-object-like-snapshot :

import com.ibm.team.repository.common.Location;

Location location = Location.itemLocation(someJazzArtefactObject, teamRepository.getRepositoryURI());                                          
URI myURI = location.toAbsoluteUri();

How does one create an instance of ILocation? The only implementation I could find of this interface is com.ibm.team.filesystem.client.internal.PathLocation which is obviously meant to be internal.

	public IShareable findShareable(String path) throws FileSystemException {

		// Canonicalize the item

		ILocation absolute = SubcommandUtil.makeAbsolutePath(config, path);

How does one create an instance of ILocation? The only implementation I could find of this interface is com.ibm.team.filesystem.client.internal.PathLocation which is obviously meant to be internal.

Discouraged access: The type PathLocation is not accessible due to restriction on required library C:\Program Files\IBM\RTC-SDK-3.0\plugins\com.ibm.team.filesystem.client_2.1.0.v20101110_2353.jar

We am writing our own build engine implementation, so we have to load the source from RTC. To load the source we're using ILoadOperation, which requires an ISandbox. To get/create a sandbox we're using com.ibm.team.filesystem.client.ISharingManager.getSandbox(ILocation, boolean), which requires ILocation as a parameter.

I had already found com.ibm.team.filesystem.client.internal.PathLocation, and my code is working. But com.ibm.team.filesystem.client.internal.PathLocation is not meant to be exposed externally, as evidenced by this compiler warning:

Discouraged access: The type PathLocation is not accessible due to restriction on required library C:\Program Files\IBM\RTC-SDK-3.0\plugins\com.ibm.team.filesystem.client_2.1.0.v20101110_2353.jar

I am just wondering, wouldn't it be easier to use the SCM tool and call that instead of recoding all the load manually?

The short answer is no: it wouldn't be easier. We experimented with the SCM command line and couldn't make it do all the things we needed it to do.

But that's besides the point, really. The fact is that RTC presents public APIs that expect certain parameters types that, as far as I can tell, are impossible to create without violating package access contraints.

I am just wondering, wouldn't it be easier to use the SCM tool and call that instead of recoding all the load manually?