My applications are all on the same server so I shouldn't have a SOP issue here.
To precise my question:
In the App1 application I have this in my bootstrap:
data-sap-ui-appCacheBuster="./"
data-sap-ui-resourceroots='{ "myapp1": "./" }'
So when App1 starts up it requests http://myserver.com/App1/sap-ui-cachebuster-info.json from the server.
Now when the applications requests a file below http://myserver.com/App1/ it is looked up in the cachebuster file and if found it is requested from the server with the timestamp from the cachebuster file in the URL:
GET http://myserver.com/App1/~20160217180545~/controller/App.controller.js
BUT:
If App1 requests a common module out of another "application" like this
GET http://myserver.com/App1/../CommonModules/something.js
This file is not found in the sap-ui-cachebuster-info.json of App1.
The mechanism would have to fetch ../CommonModules/sap-ui-cachebuster-info.json first and look this file up there.
So my question is: Can I make the app cachebuster somehow work for these cross application scenarios??
If not, how do you architect your applications? I don't believe that you "copy" a bunch of common routines every time you set u a new project. Maintenance efforts for these common routines would grow with every new project who makes use of them.
Maksim Rashchynski any idea from your side perhaps?