Hi Dinusha, What you are saying is correct according to my understanding. EMM feature should not have such entries if its not embedding such apps. Even if it does it is wrong since those apps not bound to emm context and it should get installed from that product specific features. But you could add the emm configuration files such as emm-config.xml into the emm feature. I think Chan/Harshan will look into this.
Regards, Dilshan On Wed, Oct 1, 2014 at 10:56 PM, Dinusha Senanayaka <[email protected]> wrote: > Hi Dulitha/Harshan, > > AFAIK, p2-inf should use to copy artifacts that are included feature > itself to feature install location. But in your case, jaggery apps are not > inside feature and but there is a entry in p2-inf. That's why feature > installation getting failed. You could remove the p2-inf entries and copy > store/publisher apps using bin.xml in distribution, if store/publisher not > keep inside feature. > > Regards, > Dinusha. > > On Thu, Oct 2, 2014 at 11:12 AM, Harshan Liyanage <[email protected]> > wrote: > >> Hi, >> >> For the cloud EMM version we have removed APIM features from EMM pack.We >> have done a lot of refactoring to that pack. So If you can have a look at >> EMM-Cloud pack, that would be much better. As Chan has mentioned we do a >> copy-rename operation to keep API Store, API publisher along with ES. >> >> Thanks, >> >> Best Regards, >> >> Lakshitha Harshan >> Software Engineer >> Mobile: *+94724423048* >> Email: [email protected] >> Blog : http://harshanliyanage.blogspot.com/ >> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >> lean.enterprise.middleware. >> >> On Thu, Oct 2, 2014 at 11:07 AM, Chan <[email protected]> wrote: >> >>> Hi Dinusha, >>> The .p2-inf is used as a workaround solution to keep API Publisher and >>> API Store along with ES Publisher and ES Store. I believe we have to do >>> some refactoring if our feature needs to be installed to another server due >>> to this. I am adding @Harshan to the loop too. >>> >>> Cheers~ >>> >>> On Thu, Oct 2, 2014 at 8:02 AM, Dinusha Senanayaka <[email protected]> >>> wrote: >>> >>>> Hi Dilshan, >>>> >>>> There is an entry in p2-inf of emm.feature to copy jaggery apps [1]. If >>>> you are not including jaggery apps though feature, can we remove this ? >>>> This anyway fails in p2-profile feature installation because those jaggery >>>> apps are not zipped inside feature. >>>> >>>> [1]. >>>> https://github.com/wso2/product-emm/blob/master/modules/features/org.wso2.emm.feature/resources/p2.inf >>>> >>>> Regards, >>>> Dinusha. >>>> >>>> On Thu, Oct 2, 2014 at 4:50 AM, Dilshan Edirisuriya <[email protected]> >>>> wrote: >>>> >>>>> Hi Dinusha, >>>>> >>>>> Yes we can incooperate these. However this feature will only >>>>> concentrate on embedding few mobile components related to Android and iOS >>>>> backend portion. Unlike API manager EMM does not add Jaggery apps from >>>>> feature level. Majority of the code resides in the Jaggery app. If those >>>>> needs to be reused I assume we have to separate out the Jaggery modules >>>>> instead and reuse it in AppManager rather than spliting the EMM feature >>>>> into few. +1 for adding emm related configuration into the feature. >>>>> >>>>> Regards, >>>>> >>>>> Dilshan >>>>> >>>>> On Wed, Oct 1, 2014 at 11:44 AM, Dinusha Senanayaka <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi EMM Team, >>>>>> >>>>>> Currently, EMM has only a aggregated feature [1] which contains UI >>>>>> (Jaggery) and all backend modules. Since we are trying to integrate EMM >>>>>> functionalities into App Manager, can we divide this into feature >>>>>> categories and have several features? . So that we could include only the >>>>>> necessary bundles into App Manager. Also we need to include all EMM >>>>>> related >>>>>> configuration files to be copy from feature instead of keeping them in >>>>>> product level. >>>>>> >>>>>> [1]. >>>>>> https://github.com/wso2/product-emm/blob/master/modules/features/org.wso2.emm.feature/pom.xml >>>>>> >>>>>> >>>>>> Regards, >>>>>> Dinusha. >>>>>> >>>>>> -- >>>>>> Dinusha Dilrukshi >>>>>> Senior Software Engineer >>>>>> WSO2 Inc.: http://wso2.com/ >>>>>> Mobile: +94725255071 >>>>>> Blog: http://dinushasblog.blogspot.com/ >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Dilshan Edirisuriya >>>>> Senior Software Engineer - WSO2 >>>>> Mob: + 94 777878905 >>>>> http://wso2.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> Dinusha Dilrukshi >>>> Senior Software Engineer >>>> WSO2 Inc.: http://wso2.com/ >>>> Mobile: +94725255071 >>>> Blog: http://dinushasblog.blogspot.com/ >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Chan (Dulitha Wijewantha) >>> Software Engineer - Mobile Development >>> WSO2 Inc >>> Lean.Enterprise.Mobileware >>> * ~Email [email protected] <[email protected]>* >>> * ~Mobile +94712112165 <%2B94712112165>* >>> * ~Website dulitha.me <http://dulitha.me>* >>> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >>> *~Github @dulichan <https://github.com/dulichan>* >>> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >>> >> >> > > > -- > Dinusha Dilrukshi > Senior Software Engineer > WSO2 Inc.: http://wso2.com/ > Mobile: +94725255071 > Blog: http://dinushasblog.blogspot.com/ > -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
