On Mon, Jun 10, 2013 at 6:06 PM, Afkham Azeez <[email protected]> wrote:
> I suggest that we remove all orbits which simply wrap 3rd party jars from > our main code repo, and have a separate repo for that. All such orbit > bundles will immediately be graduated, and deployed into the WSO2 Maven > repo. If there is an issue with such an orbit bundle, which is a rare > occurrence, you have to increment the orbit version of that bundle. > +1 for this. We need to keep in mind that kernel is planing on moving into git. After that its the complexity of component, features structure that gives the most trouble IMO. > > Next step would be to start collapsing the components. For example, all > the 50 mediator components will be collapse into the mediator BE & mediator > FE components. > > We also need to greatly simplify the branching. When we collapse > components & have a smaller number of components, branching will become > much simpler. > Have a suggestion. > > > > On Mon, Jun 10, 2013 at 5:32 PM, Sagara Gunathunga <[email protected]>wrote: > >> >> >> >> On Mon, Jun 10, 2013 at 3:32 PM, Afkham Azeez <[email protected]> wrote: >> >>> Unfortunately, our code repo structure & build structure is insanely >>> complex. This is the reason why it is so hard to prevent build breaks. We >>> need to think of a much simplified structure. Too much complexity always >>> leads to human error. We need to simplify everything, starting from the >>> repo structure. >>> >> >> In fact during each and every release we have to spend significant amount >> of time to resolve issues introduced by repo structure & build structure >> themselves. If we can make them simple we can have very smooths release >> cycles and on time releases. >> >> +1 to prioritize this as an urgent requirement. >> >> Thanks ! >> >> >> >>> >>> Azeez >>> >>> >>> On Mon, Jun 10, 2013 at 3:20 PM, Sriskandarajah Suhothayan < >>> [email protected]> wrote: >>> >>>> >>>> >>>> >>>> On Mon, Jun 10, 2013 at 1:48 PM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> Folks, >>>>> Can somebody let me know how to do this? I seem to have forgotten the >>>>> process, and everuthing looks very confusing. Some orbit bundles are in >>>>> trunk, some are in different branches... it is not easy to find where the >>>>> Hazelcast orbit is :( >>>>> >>>>> The Hazelcast orbit[1] was removed as its now graduated >>>> >>>> This orbit bundle will be needed by all components & the kernel. >>>>> >>>> >>>> If you are directly using the the lib to build the bundle then that >>>> need to be added to the main orbit >>>> The orbits under the dependencies are only used to bundle the relevant >>>> dependencies >>>> >>>> Suho >>>> >>>> [1] >>>> https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/hazelcast/2.2.wso2v1/ >>>> >>>> >>>> >>>>> >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>** >>>>> email: **[email protected]* <[email protected]>* 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* >>>>> * >>>>> * >>>>> *Lean . Enterprise . Middleware* >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *S. Suhothayan >>>> * >>>> Associate Technical Lead, >>>> Management Committee Member, Data Technologies Team, >>>> *WSO2 Inc. *http://wso2.com * >>>> <http://wso2.com/>* >>>> lean . enterprise . middleware >>>> >>>> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >>>> twitter: http://twitter.com/suhothayan | linked-in: >>>> http://lk.linkedin.com/in/suhothayan* >>>> * >>>> * >>>> >>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **[email protected]* <[email protected]>* 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* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sagara Gunathunga >> >> Senior Technical Lead; WSO2, Inc.; http://wso2.com >> V.P Apache Web Services; http://ws.apache.org/ >> Linkedin; http://www.linkedin.com/in/ssagara >> Blog ; http://ssagara.blogspot.com >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* 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* > * > * > *Lean . Enterprise . Middleware* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
