IMHO the value of splitting the source code into multiple repositories
would really come up if it were possible (and practical) to develop
NetBeans modules independently, for example, clone a module repo, work
on it, then run/test it using an already built IDE, then release the
module update (increment the version, etc). And when the time comes to
release new NetBeans version, build script would pull all the pieces
together.
Then again, they don't necessarily need to be git submodules as they
could prove to be a little hard to use due to having to link them all
using git and re-link on each update. It would suffice if the build
script just knew where to get them (eg. repo URLs), then if a specific
cluster is build, it wouldn't be necessary to download all of them.
Regards.
06.09.2020 16:15, Eric Bresie wrote:
While reading an article recently, the topic of git submodules came up, which I
started looking up the topic (1).
Given the size of the netbeans code base and the complexity of other projects
inclusion like the specific plugin/clusters, etc., I was wondering if it’s
worth considering breaking out some of these elements into separate submodule
projects.
This would reduce the overall size of the netbeans project (but the placeholder
submodule - normally empty until submodule is pulled) and would allow each
submodule to be managed independently.
The drawback may be a little learning curve on submodule usage which may add to
some issues initially as well as a few extra steps during builds.
(1) https://git-scm.com/book/en/v2/Git-Tools-Submodules
Eric Bresie
ebre...@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
