I've been refactoring shared libs and some builds that I have, and started using component load rules to ease the amount of download needed per build, that part is working just fine and the builds are buzzing along faster than ever.

http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=/com.ibm.team.build.doc/topics/r_scm_build_loadrules.html

My question: Can I maintain the path? Otherwise I am stuck with potentially different relative paths to the same files based on the load rules!

Load Rule

versionableName=/sharedlibs/junut.jar

versionableName=/sharedlibs/log4j.jar

versionableName=/project1/

versionableName=/project4/build.script

Result:
/-
-project1/
-junit.jar
-log4j.jar
-build.script

Desired Result:
/-
-/project1/
-/sharedlibs/junut.jar
-/sharedlibs/log4j.jar
-/project4/build.script

In this case all my build scripts are consistent can be oblivious to the potential load rules being used, and work the same everywhere. Perhaps there is another way to do this or I am going it about it wrong, so any suggestions or advice is appreciated.

-Sean