We (5 devs) have been working for years on a project consisting of 2 Netbeans projects:
- The core, c++ (1 main dev, 3 supporting, I will be added later on). The core can run on it's own through command line.
- The gui, java (just me for now). Calls core functionality through a JNI layer or by invoking executables built from the core.
We've reached a point where we would like to start using version control. No one in the team has any (thorough) experience with that, but I (a complete noob) was assigned to investigate and train the team. I've done a lot of research, set my mind to Git and now I'm trying to figure out the best workflow and infrastructure.
I was thinking of 1 repository for the whole project because we are used to having our version number and release notes in sync, in other words, if either the core or the gui is updated, the whole thing will be released as a new version into production. I imagine having only 1 repository greatly simplifies this.
My question right now: Is it possible to have those 2 separate Netbeans projects inside 1 Git repository and still be able to fully utilize Netbeans' Git support, or are 2 repositories the only course of action?
When using Git only through command line, I don't see any trouble, but using Git (also) through Netbeans is a must for our team and as far as I know, 1 Netbeans project equals 1 Git repository ...




