Hi, We are in the process of moving all Jaggery modules into a single repo named, Jaggery Extensions[1]. With this,
- A Jaggery module will be a self-contained p2 feature which can be installed via the feature manager. - All the *.js files and hostobjects which belongs to a module will go under that modules directory. - Each module will be versioned and released separately - All reusable codes should be written as modules and hosted there Along with this, Jaggery github source is restructured as well. i.e. At the moment we ship following Jaggery modules as a part of the Jaggery core and sources are kept in the Jaggery master. - process - module to access environment/system variable - email - send emails - carbon - access all carbon related apis - ws - invoke web services - oauth - oauth support - gadget - gadget embedding support - i18n - i18n support - uuid - uuid generation Above modules too will be moved to [1]. Further, Jaggery Extensions project[1] will depend on Jaggery master. Hence, we are thinking of not shipping above modules as a part of Jaggery core. Anyone who want those modules, can install them either via a feature manager or p2-profile gen during the build. In the jaggeryjs.org, we will host a different distribution with all needed modules. This distribution will also be there in git master and Jaggery extensions source will be fetched via a submodule. /Ruchira [1] https://github.com/wso2/jaggery-extensions -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* *email: [email protected] <[email protected]>, blog: ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, mobile: +94 77 5493444*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
