Stephan van Hulst wrote:
In NetBeans it would be similar to a "project group". I don't know how other IDEs call it. Usually IDEs don't store project groups in separate files, but somewhere in the IDE configuration settings instead.
In Eclipse, it would be the ".project" file, which defines the project. In IntelliJ, they kept 2 files - one for the project itself, and one for the individual user's saved project context. That is, remembering stuff like what files a user was looking at and other things to make life easier, but not actually required to build the project.
Because the filenames used by Eclipse and IntelliJ are different, I have on occasion built multi-IDE projects, where a developer could use either Eclipse or IntelliJ to do their work.
But my standard for production builds is that they be done from the command line (for example via
Maven, and possibly launched by
Jenkins), none of those files were required or used for production builds.