Darren, I had a quick look at your four submissions, Is there no dependency between them? if so, can you add those to the review requests?
thanks, Daan On Wed, Sep 18, 2013 at 1:25 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > sounds great Darren, > > By component, you mean maven project or some larger chunk like > distribution package? (did i miss this definition somewhere or do we > define the components now?) > > regards, > Daan > > On Wed, Sep 18, 2013 at 12:10 AM, Darren Shepherd > <darren.s.sheph...@gmail.com> wrote: >> Currently ACS code is fairly modular in that you can add plug-ins to ACS to >> extend most functionality. Unfortunately ACS is not packaged in a modular >> way. It is still delivered essentially as one large unit. There are many >> reason for this but one large barrier to modularizing ACS is that the >> Spring configuration is managed as one large unit. >> >> I propose that we break apart the Spring XML configuration such that each >> component contributes its own configuration. Additionally each component >> will be loaded into its own Spring ApplicationContext such that its beans >> will not conflict with the wiring of other beans in ACS. This change will >> lay the foundation for a richer plugin model and additionally a more >> distributed architecture. >> >> The technical details for this proposal can be found on the wiki [1]. >> >> Darren >> >> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Modularize+Spring
