I think I raised a similar question some other time but wanted to ask... When is it appropriate to bring in a module into the mainline netbeans source (i.e. php, cnd, etc.) and when should it be instead provided as an external project and/or plugin?
I ask because of the wealth of “contrib” items out there which may be worth migrating to external “plugins” (i.e. UML, Collaborative”, etc.) or integrated into the mainline (i.e. cnd, python, etc.) I assume this is something that is a case by case basis. Assume to include into the mainline vs plugin have pros and cons like For mainline inclusion Pro - Provides new major functionality by default in a given build - Becomes part of the Netbeans product as a whole Con - Adds to the size of the mainline codebase and/or the delivery product - Cluster may be more susceptible to mainline changes For plugin delivery Pro - Keeps size of mainline codebase smaller - Allows independent delivery - Potentially allows “plugin” specific support (maybe even commercial ??) Con - Requires mainline version compatible (i.e. check for compatible and/or updates in line with given release) as applicable - Not as closely couple and requires separate installation What do you think? Eric Bresie ebre...@gmail.com (mailto:ebre...@gmail.com)
