Folks, since there seems to be no objections, we are proceeding with this proposal.
Regards, /Nuwan On Fri, Jun 15, 2012 at 12:16 PM, Nuwan Bandara <[email protected]> wrote: > Hi All, > > As we are planing to move Jaggery code to GitHub (before Jaggery 1.0 > release), we will have to separate the jaggery modules from carbon > components and features. As previously agreed upon, jaggery group id will > be org.jaggeryjs > > So we will be removing jaggery components and features from the current > SVN structure, and will be adding adding them into products/jaggery so the > jaggery product svn structure will look like, > > . > ├── modules > │ ├── apps > │ ├── *components* > │ ├── distribution > │ ├── *features* > │ ├── integration > │ ├── p2-profile-gen > │ └── styles > ├── pom.xml > ├── svnignore.txt > └── target > └── timestamp > > So the removed components will reside in products/jaggery/modules/components/ > and once Carbon is released we will move this to GitHub and remove from > WSO2 SVN entirely (but will put an external to Git) > > -- > *Thanks & Regards, > > Nuwan Bandara > Associate Technical Lead & Member, MC, Development Technologies > WSO2 Inc. - lean . enterprise . middleware | http://wso2.com > blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> > -- *Thanks & Regards, Nuwan Bandara Associate Technical Lead & Member, MC, Development Technologies WSO2 Inc. - lean . enterprise . middleware | http://wso2.com blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
