mercredi 8 avril 2015

Generated paths for manifest and app.json

After building an application with cmd the microloader assumes that the app.json resides in the same folder as the "index.html".




Code:



var Ext=Ext||{};Ext.manifest=Ext.manifest||"app.json";Ext=Ext||{};




Inside the app.json the compiled application and its resources are always relative from this app.json




Code:



"js":[{"path":"app.js"}],"css":[{"path":"resources/MyApp-all.css"}


How can I tell cmd to generate another path because my final application will use a different path when including the microloader? Currently I'm using grunt-string-replace to do this.




HTML Code:



<script type="text/javascript" src="/deployment/build/production/Mypp/microloader.js"></script>


So the generated paths should be like this:




Code:



var Ext=Ext||{};Ext.manifest=Ext.manifest||"/deployment/build/production/MyApp/app.json";Ext=Ext||{};



Code:



"js":[{"path":"/deployment/build/production/MyApp/app.js"}],"css":[{"path":"/deployment/build/production/MyApp/resources/MyApp-all.css"}







Generated paths for manifest and app.json

Aucun commentaire:

Enregistrer un commentaire