Hi Ruwan, There are only two jaggery-modules that belongs to AppManager (apistore [Need to rename] and appmgtpublisher). All other modules already having separate feature for each. We are using 1.0.0 versions of them which were already released and we cannot make changes to them by the time we were releasing AppM. Modules that had some fixes/changes were only took to AppM product level to make distribution. Since appmgt.store and appmgt.publisher features should be able to work with feature installation to other products, we had to add those modules inside feature as well.
Anyway, we could remove the modules that we keep in product level and use them from the appmgt.store/publisher feature. Same time we need to check whether we can get rid of keeping them inside AppM feature by updating to new jaggery-module versions if they having new versions. Regards, Dinusha. On Mon, Jul 6, 2015 at 4:57 AM, Ruwan Abeykoon <[email protected]> wrote: > Hi AppManager team, > > I found at least thee locations in AppM code base where the same module is > copied. > 1. product-app-manager/modules/jaggery-modules > 2. > carbon-appmgt/features/appmgt/org.wso2.carbon.appmgt.publisher.feature/src/main/resources/jaggery-modules > 3. > carbon-appmgt/features/appmgt/org.wso2.carbon.appmgt.store.feature/src/main/resources/jaggery-modules > > Can we create new feature for them (something like a UI core feature), > Since all the modules in Store/Publisher/Social need to be deployed on the > "<CARBON_HOME>/modules". > > > Cheers, > Ruwan > > -- > > *Ruwan Abeykoon* > *Architect,* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: [email protected] > phone:(+94) 777739736 > -- Dinusha Dilrukshi Associate Technical Lead 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
