I initially considered about this option too. IMO I think breaking modules based on each cloud vendor is simple specially for end users perspective. As an example a users write his code for nuvem-api ( its a single module) then if he decide to host app on GAE he can bring **nuvem-google as a implementation dependency in case if he want to move to a another cloud vendor he can simply remove nuvem-google and possible to bring nuvem-X dependency. Also for API i think its better to have it as a single Jar file.
But in case if a user want to have different cloud components from different vendors within a single app then having modules based on features/services is more meaningful to him. In my point of view assembling cloud component from a single vendor for a single app is the expected common scenario specially considering $$ option :) Thanks ! On Thu, Mar 10, 2011 at 2:37 AM, john pradeep <yehohan...@gmail.com> wrote: > Hi, > +1 from my side, just a quick question though. > > would it not be a good idea considering to break the modules based on the > features/services? for example as shown below. > > nuvem-user (API) > nuvem-user-google > nuvem-user-standalone > > nuvem-xmpp (API) > nuvem-xmpp-google > nuvem-xmpp-standalone > > Thanks, > John > > On Thu, Mar 10, 2011 at 2:10 AM, Sagara Gunathunga < > sagara.gunathu...@gmail.com> wrote: > > > Hi Folks , > > > > I believe Nuvem has potential to get higher number of modules in future > so > > it is important to follow some short of convention when adding new > modules > > to the code base. I'm suggesting to restructure code base as follows > > > > * Top Level modules * > > > > nuvem-api > > nuvem-standalone > > nuvem-google > > nuvem-amazon > > -------------------- > > ------------------- > > nuvem-samples > > nuvem-parallel (*) > > > > > > > > (*) - At the moment we can keep nuvem-parallel module also as a top level > > module. > > > > By considering complexity we can decide whether to have sub modules > under > > the top-level modules or not. But definitely I believe it is required to > > move sample applications from top level to nuvem-samples module. > > > > > > Secondly I believe we can enhance Maven support for GAE samples by adding > > maven-gae-plugin [1] , this enables to run apps locally and deploy using > > Maven. I already mange to deploy Nuvem samples on GAE using this plug-in. > > Also I think we can integrate nuvem-parallel tests into Maven build using > > Maven Exec plug-in. > > > > > > Any thoughts ..... ? > > > > > > [1] - http://www.kindleit.net/maven_gae_plugin/ > > > > > > > > Thanks ! > > > > > > -- > > Sagara Gunathunga > > > > Blog - http://ssagara.blogspot.comance > > Web - http://people.apache.org/~sagara/ is iportent > > > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
