Under dependency governance, the plan is to show the dependency graph, so that when an upstream dependency changes, we would know what downstream code would be affected.
On Sat, Jan 18, 2014 at 9:50 PM, Hasitha Hiranya <hasit...@wso2.com> wrote: > Hi, > > +1 for the categorization. > Is there a way to make a Tree graph or something displaying > the dependency graph? And maintain it somewhere? In that way in the long > run we will have a clear visibility (when new components/features added). > > Thanks > > > On Sat, Jan 18, 2014 at 6:30 PM, Eranda Sooriyabandara <era...@wso2.com>wrote: > >> Hi All, >> Here is the component categorization. >> >> Remove forever >> >> - qpid >> - rest-api >> - mashup >> >> Need to move to relevent products >> >> - stratos >> - cloud-controller >> - appfac >> - ec2-client >> - cg >> >> >> Graduate to nexus >> >> - mapred >> - email-verification >> - captcha-mgt >> - tryit >> - wsdlvalidator >> - java2wsdl >> - soap-tracer >> - zeroconf >> - wsdl2code >> - wsdl2form >> - schema-generator >> >> >> carbon-feature-registry >> >> - registry >> >> >> carbon-feature-governance >> >> - governance >> >> >> carbon-feature-identity >> >> >> - identity >> - authenticators >> - claim-mgt >> - remote-usermgt >> - user-manager >> - user-stores >> - sts >> - policy-builder >> - policy-editor >> - security >> - directory-server-manager >> - idp-mgt >> - ldap-server >> - profile-mgt >> - cassandra-userstore >> - issue-tracker >> >> >> carbon-feature-mediation >> >> - mediation >> - mediation-initializer >> - mediation-statistics >> - mediation-tracer >> - mediators >> - messagebox >> - message-relay >> - mex >> - priority-mediation >> - sequence-editor >> - synapse-artifact-uploader >> - synapse-config-admin >> - synapse-registries >> - proxy-admin >> - localentry >> - endpoint >> - view-flows >> - xfer >> - xkms >> >> >> carbon-feature-analytics >> >> - analytics >> - bam2 >> - data-agents >> - transport-statistics >> - system-statistics >> - dashboard >> - dashboard2 >> - gadget-ide >> - gadgets >> - gauges >> - health-monitor >> >> >> >> carbon-feature-data >> >> - data-services >> - dbconsole >> - data-sources >> - ndatasource >> >> >> carbon-feature-apis >> >> - apimgt >> - appmgt >> >> >> carbon-feature-business-process >> >> - business-processes >> - multiple-instance >> - coordination >> >> carbon-feature-business-messaging >> >> - business-messaging >> - event >> - eventing >> - event-processing >> >> >> carbon-feature-rules >> >> - rule >> >> >> carbon-feature-deployment >> >> - webapp-mgt >> - jaxws >> - module-mgt >> - service-mgt >> - spring-services >> - application-deployers >> - application-mgt >> - axis2-repo-mgt >> - ejb-services >> - aar-services >> - jar-services >> - autoscaler >> - load-balancer >> - deployment-synchronizer >> >> >> carbon-feature-qos >> >> - throttling >> - reliable-messaging >> >> >> carbon-feature-utils >> >> - caching >> - cluster-mgt >> - unified-endpoint >> - url-mapper >> - ws-discovery >> - rss-manager >> - transaction-manager >> - transport-mgt >> - transports >> - jaggery >> - hostobjects >> - ntask >> - scheduled-tasks >> - operation-mgt >> - startup >> - reporting >> - data-bridge >> - doc-request-processor >> - logging >> - admin-mgt >> - remote-tasks >> - andes >> - cassandra >> - cassandra-explorer >> - cassandra-search >> - hdfs >> >> >> When adding a component to a project please note the following. >> >> 1. utils project should be not depend on any other projects. Any >> other project can depend on another project but it shouldn't be cyclic. >> 2. If any component is not going to change we can graduate to the >> nexus without making everyone to build the source. I have identified >> certain components, but if you think it source will be changed then we >> still can add it to the related project. >> >> Your comments and suggestions are mostly welcome. Project leads please >> confirm the structure. >> >> >> thanks >> Eranda >> >> >> >> On Sat, Jan 18, 2014 at 11:09 AM, Eranda Sooriyabandara >> <era...@wso2.com>wrote: >> >> Hi Sagara, >> >> >> On Sat, Jan 18, 2014 at 11:02 AM, Sagara Gunathunga <sag...@wso2.com>wrote: >> >> >> >> >> On Sat, Jan 18, 2014 at 10:31 AM, Afkham Azeez <az...@wso2.com> wrote: >> >> Shall we name those as; >> >> - carbon-feature-registry >> - carbon-feature-governance >> - carbon-feature-identity >> - carbon-feature-mediation >> - carbon-feature-analytics >> - carbon-feature-data >> - carbon-feature-apis >> - carbon-feature-business-process >> - carbon-feature-business-messaging >> - carbon-feature-rules >> - carbon-feature-deployment >> - carbon-feature-qos >> - carbon-feature-utils >> >> Do you have a document to see the mapping among above projects and >> current components ? If not we need to crate a one and review by all >> products teams WDYT ? >> >> >> I'll be sending the categorized list of components to this thread then >> the project teams can review and add the ideas here. >> >> thanks >> Eranda >> >> >> >> >> Thanks ! >> >> >> >> and also have; >> * carbon-product-appserver >> * carbon-product-esb >> >> and so on. >> >> Also; >> carbon-p2-repo >> >> carbon-platform-integration-tests >> >> >> >> >> On Sat, Jan 18, 2014 at 9:12 AM, Eranda Sooriyabandara >> <era...@wso2.com>wrote: >> >> Hi Infra, >> Can we have following projects created in the git repo. Additionally >> >> - registry >> - governance >> - identity >> - mediation >> - analytics >> - data >> - apis >> - business-process >> - business-messaging >> - rules >> - deployment >> - qos >> - utils >> >> Additionally please add me (erandasooriyabandara) to WSO2 member list. >> >> thanks >> Eranda >> >> >> >> >> -- >> >> *Eranda Sooriyabandara*Senior Software Engineer; >> Integration Technologies Team; >> WSO2 Inc.; http://wso2.com >> Lean . Enterprise . Middleware >> >> E-mail: eranda AT wso2.com >> Mobile: +94 716 472 816 >> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >> Blog: http://emsooriyabandara.blogspot.com/ >> >> >> >> >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Hasitha Abeykoon* > Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **az...@wso2.com* <az...@wso2.com> * cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
