The first time a project is to be saved, a Save Project As file chooser will be displayed, requesting the filename and location of where you want to save the project to.
Once a project has been saved once, selecting File | Save will save the project to disk immediately without a need to prompt you. To save the current project to a different project file, select File | Save As and you will be prompted for the new project file location. Once you save the project to this new location, all further changes and saves will be to this new location.
Save location
Projects can be saved anywhere on disk. The save location does not need to be relative to your program's class files. The save location does not affect the program's working/runtime directory.
File extension
When supplying a file name for the project, a default '.bsp' extension will be added to the filename if you do not supply an filename extension. The extension itself is not important to BugSeeker and serves mainly to allow you to identify which files are project files; BugSeeker will open any named file as long as it is a valid BugSeeker project.
What's stored in projects?
All project settings you see in the Project Properties dialog are saved with the project. This includes the classpath and sourcepath settings. Breakpoints, their properties, and their locations are also stored in the project as is the project's recently used file history and other miscellaneous project-specific settings.
Projects are not cross-platform
Although BugSeeker itself is cross-platform, projects created by BugSeeker most likely will not work across platforms. You will be able to load the project created on one platform on a different platform; however, you won't be able to launch a debugging session because the project's classpath entries are usually hard coded by you to refer to directories and zip or jar archives found on the platform in which the project was created on.