On Tue, Oct 17, 2017 at 10:19 PM, Stefan Seifert <sseif...@pro-vision.de> wrote: > > >>-----Original Message----- >>From: Justin Edelson [mailto:jus...@justinedelson.com] >>Sent: Tuesday, October 17, 2017 3:04 PM >>To: dev@sling.apache.org >>Subject: Re: [git] Migration scheduled for 18 Oct, 22:00 CEST and final >>notes >> >>On Tue, Oct 17, 2017 at 8:49 AM Robert Munteanu <romb...@apache.org> wrote: >> >>> >>> >>> Perhaps the people that actually work with these multi-project >>> extensions would like to comment? By a quick check we have: >>> >>> - models >>> >>> >>The models bundles can be released independently, i.e. I've done a number >>of releases of the implementation bundle without touching the API bundle. >> >>While Konrad is correct that ITs are an issue, my strong preference with >>Sling Models is to minimize the use of ITs, i.e. use them only for code >>paths which are difficult to test via a unit test, so I don't really see >>that as an issue. > > +1 to stick with git-repo-per-module > > same applies to caconfig - 95% of tests are unit tests, only few integration > tests to make sure all is working together > > stefan
+1 to stick with git-repo-per-module regards, Karl -- Karl Pauls karlpa...@gmail.com
