> On Oct 7, 2016, at 11:23, Wade Chandler <[email protected]> wrote: > > >> On Oct 7, 2016, at 10:23, Jan Lahoda <[email protected] >> <mailto:[email protected]>> wrote: >> >> I guess the question is what do you consider a core part. I think it would >> be OK to not keep history in the "main" repo for modules that were placed >> into separate repositories, like: >> http://hg.netbeans.org/community-visualweb/ >> <http://hg.netbeans.org/community-visualweb/> >> (as far as I can tell, the history is kept in the split up repositories.) >> But is e.g. the Java support a core part? C/C++ support? PHP support? >> > > The core IDE and even the main build can be split from the other specific > feature support, regardless of what is said to be in the core, and even then, > some repos may not “stand alone” for the sub-components/modules IMO with > regard to the the main build as a sibling or parent; this gets into git > sub-modules as a way to break up the size as well as what one has to checkout > to work on a specific piece of functionality. So, the basic pieces to just > get the platform up and running, and the build going, is 1 big sub-set to me. > Then, Java specific support could be another. It could split on SE and EE > though. Next, PHP, that seems independent. HTML/Web/etc…another. Groovy > stands out as another. I’m sure that can keep going. Then, if the repos were > essentially: > > netbeans-core (however it is decided) > netbeans-java > netbeans-javaee > netbeans-groovy > netbeans-php > netbeans-c > netbeans-nodejs (or what ever the name is) > …etc > > Then that seems manageable to me. There could then be netbeans-main which, > with a little restructuring, has all those which make up the NetBeans release > as an entire structure with git sub-modules. It could be it breaks different. > It could be like this > netbeans-main (has what we would call core in it…along with current build.xml > and nbbuild…this would allow the current build system to keep working without > any or much rework I think) > netbeans-java > netbeans-javaee > … etc etc > > and netbeans-main has git sub-modules for all of what is the “NetBeans > release”. This would take some work undoubtedly. Too, the history can be > interesting in these cases.
Obviously this should be examined more, but a list of everything from a recent main-golden clone can be inspected with a "ls -d *” command from inside the project directory. Other than core, which one would have to piece mill based on dependencies, and break them apart, a good lot jump out as things which could be better split IMO; cnd.*, much of bugtracking if not all depending on how the exception reporter is handled/redone, the library wrapper plugins such as c.google.guava, clearcase, cloud.*, collab.*, cordova.*, db.*, debugger.*, and many others. Wade
