Project jpr structure
13984Dec 11 2003 — edited Dec 11 2003
Currently (v9.0.3.3), JDeveloper projects are stored in a single jpr file (using xml). This stores pretty static project settings including libraries used, project dependencies as well as dynamic settings that are very user specific such as the most recently used package.
I suggest that future versions of JDeveloper break up the content into two seperate files: a static one and a dynamic one. The static project file could then be stored in a source control system while the dynamic file doesn't need to be stored in source control. This would minimize the pain of having continually changing project files due to user specfic settings. Under this process, if you check out the source code and don't have a dynamic settings file then one could be automatically generated.