Olá Bruno! thanks *a lot* for reviewing the experimental branch for modulazitation, really much more than appreciated!
And thanks a lot for setting up the Jenkins job, it does help! Have a nice WE, all the best, -Simo http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Fri, May 31, 2013 at 6:57 PM, Bruno P. Kinoshita <brunodepau...@yahoo.com.br> wrote: > Hi Simo! > > I liked the project structure, it's looking like the new structure that Matt > created in commons-functor [1], with a API project, one module for each > algorithm family and other modules for utility projects, like benchmark tests. > > I think we'll have to update the website, since now under Project > Documentation / Project Modules, the links to the submodules pages are broken. > > So kudos for the great work and my +1 for the modularization of > commons-graph. Since I'm not very familiar with commons-graph code base and > haven't used it in any project yet, probably other's comments will be > important on this thread too. > > Side note, I noticed that there are some TODO's, mainly in Javadocs. So I've > set up a job in Jenkins [2] with the Maven site + open tasks (FIXME, TODO and > TBD). I'll read the open tasks later to see if I can work on any of them, but > I think I'll wait for the modularization branch to be merged first :) > > Cheers > > [1] http://svn.apache.org/viewvc/commons/proper/functor/trunk/ > [2] http://builds.tupilabs.com/job/commons-graph-modularization/1/tasksResult/ > > Bruno P. Kinoshita > http://kinoshita.eti.br > http://tupilabs.com > > > --- Em ter, 28/5/13, Simone Tripodi <simonetrip...@apache.org> escreveu: > >> De: Simone Tripodi <simonetrip...@apache.org> >> Assunto: [Followup][Graph] the future of commons-graph and modularization >> Para: "Commons Developers List" <dev@commons.apache.org> >> Data: Terça-feira, 28 de Maio de 2013, 12:06 >> Hi all guys, >> >> here it is my proposal[1], see r1486948. >> >> It has been quiet hard since he did not think in therms of >> separated >> modules, so I took the freedom to relocate some classes here >> and >> there. It is a experimental branch anyway, the purpose is >> just >> demonstrating the PoC. >> >> Looking forward to read your feedbacks! >> >> Many thanks in advance, all the best, >> -Simo >> >> [1] >> http://svn.apache.org/repos/asf/commons/sandbox/graph/branches/modularization/ >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> >> On Sun, May 26, 2013 at 5:35 PM, Simone Tripodi >> <simonetrip...@apache.org> >> wrote: >> > Hi all, mates, >> > >> > after a long while I haven't touched commons-graph, I >> had the >> > opportunity to get influenced by some activities at my >> paid work that >> > made me think twice on what as been already done in >> that component, >> > and would like to bring new experiences in. >> > >> > So, what I still like about it: >> > >> > * graph APIs: the use of generics make the usage >> of graphes >> > extensible and adaptable; >> > >> > * fluent APIs: this is the most powerful feature >> IMHO that simplifies >> > the APIs usage; >> > >> > What I *don't* like anymore: >> > >> > * poor modularization: commons-graph is ATM a big >> fat monolith; >> > >> > * one single entry-point; for each new family of >> algorithm(s), new >> > methods have to be added in the main Commons-Graph >> class. >> > >> > What I would like to propose to work _in a separated >> branch_, is >> > trying to split the big monolith in smaller modules and >> separate APIs >> > from related implementation as much as possible. >> > >> > Questions are: >> > >> > * WDYT? :) >> > >> > * About release process: would it be acceptable, >> here in commons, >> > release a single module - the only one that has been >> changed, I mean - >> > without releasing the whole project? >> > >> > * In case the answer to previous question is >> "no", would it make >> > sense moving commons-graph to the Incubator (and >> possibly to TLP)? >> > >> > TIA, all the best! >> > -Simo >> > >> > http://people.apache.org/~simonetripodi/ >> > http://simonetripodi.livejournal.com/ >> > http://twitter.com/simonetripodi >> > http://www.99soft.org/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org