Peace~ --- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware ~Email [email protected] ~Mobile +94712112165 ~Website dulithawijewantha.com ~Blog blog.dulithawijewantha.com ~Twitter @dulitharw
On November 28, 2013 at 10:39:26 AM, Madhuka Udantha ([email protected]) wrote: On Thu, Nov 28, 2013 at 2:01 AM, Ruchira Wageesha <[email protected]> wrote: Hi Dulitha, What I see is, every Jaggery app should be a p2 feature which can be installed into whatever product they want. +1 You guys will always use either a released app or the snapshot. In both cases, you will have to build app feature first and your product next, where you get it up to date. At the moment, those apps have a few dependencies to other carbon features etc. Due to those case, p2 is most suitable answer for it We can complete p2 with submodules approach. p2 will copy the necessary things to run the app. The app itself will be copied by the store builder with their own store app customized. Another point I’d like to mention is - in a real deployment a customer would modify the store app. Without a submodule approach there is no way to get the module changes made by the current store app by a customized store. Also I searched for using git external and found out that it cannot be done. [1] - http://stackoverflow.com/a/18194523/813471 and you will have to get those changes as well with the up to date Jaggery sources. Hence, just having a git sub module will not work as expected and correct model is to have self contained features. As I had mentioned in one of my previous mails, whole store has bundled as a feature now, where you can install it using p2 and get everything up to date, not just the app sources. Further, that feature contains both publisher and store apps, but if it's needed we can make them as separate features. On Wed, Nov 27, 2013 at 8:30 AM, Dulitha Wijewantha <[email protected]> wrote: Hi guys, What do you think about having git submodules for apps? For an example in the Store project it has the apps in the jaggeryapps folder. If we have a separate git project for each app (publisher git repo) it would easy for people to get changes of the particular jaggery app. An example would be - I am having the store jaggery app in the mobile server. I want to get the latest changes from the generic store. Right now I have to get a copy of the generic store and put my features into that. If we have a separate git project for the generic store app I can do a git pull and auto merge the generic store changes. WDYT? -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware ~Email [email protected] ~Mobile +94712112165 ~Website dulithawijewantha.com ~Blog blog.dulithawijewantha.com ~Twitter @dulitharw -- Ruchira Wageesha Associate Technical Lead WSO2 Inc. - lean . enterprise . middleware | wso2.com email: [email protected], blog: ruchirawageesha.blogspot.com, mobile: +94 77 5493444 -- Madhuka Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com Mobile: +94774066336 Blog: http://madhukaudantha.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
