What if my development team uses tools other than JDeveloper?
If you are using JDeveloper, you should version at the application level. This assures that your .jws and .jpr configuration files are included in source control, especially important if you have dependencies between projects. But what if not all your development team are using JDeveloper? Perhaps you have some team members that use Eclipse or another IDE as well as JDeveloper? In this case it is important to ensure that you still place both your ‘jws’ and your ‘jpr’ files under source control. Why? Because JDeveloper looks at the state of those files to decide what versioning menu options it makes available. For instance, say the projects making up an application had been imported into SVN but the root level application folder and the .jws file had not been included. Perusing the versioned files through the SVN Navigator repository you would notice that there was no .jws in the application root folder. To overcome this you would create a new empty application and check out the JDevelo
