Using the CMS Filesystem

Status information in the CMS Explorer

Form files and Java files

Status information in the Source Editor

A mounted CMS filesystem appears in the NetBeans Explorer as a separate top-level node and tree. All CMS status information and all CMS commands are available exclusively from the CMS node of the Explorer ("CMS Explorer") or from a separate CMS Versioning window.

You can execute CMS commands for one or more selected files in the following ways:

Status information in the CMS Explorer

Under the CMS mount point, all files display a status annotation in the CMS Explorer. These annotations, consisting of a status caption and a badge icon, change as necessary to reflect the current source control status of each file. Badge icons can be as follows:

 
Badge
Meaning
 
Locally added or modified
 
Needs to be checked out
 
Up to date

The bracketed caption (next to each file name) shows the file status and file generation information. This status changes with each CMS command you apply. The following table shows what file status means with respect to the local* file and the CMS library.:

CMS Support Module
Explorer Status

Local* copy
of file in
working directory

File of same name exists in CMS library

File is reserved (checked out from library)

Local copy
differs from
CMS library version

No Local Copy

No

Yes

No

n/a

No Local Copy, Reserved; n

No

Yes

Yes

n/a

Locally Added

Yes

No

No

n/a

Up-to-Date; n

Yes

Yes

No

No

Locally Modified; n

Yes

Yes

No

Yes

Up-to-Date, Reserved; n

Yes

Yes

Yes

No

Locally Modified, Reserved; n

Yes

Yes

Yes

Yes

*A local copy of a file is a file that exists in the mounted NetBeans filesystem (regardless of its CMS library status).

Once you have obtained a local copy of a file - using either the Check Out (Reserved) or Get Latest Version (Fetch) commands, you can start working with the file. You can move files into existing directories (folders), or create new directories and move the files there, or you can leave the files directly under the root. Once a file is put into a particular directory, it will remain there until you either move or delete it.

Up-to-Date
A file is up to date when the file in the CMS Explorer is identical to the file in the CMS library. This is the case after you use the following commands:

Up-to-Date Reserved
When you use the Check Out (Reserve) command, it appears in the CMS Explorer as [Up-to-Date Reserved;<n>], where <n> is the CMS generation number.

Locally Modified
Once you modify a file and save it, its status changes to [Locally Modified;<n>]. The <n> generation number indicates that the file is under source control. You may need to use the Refresh command to see this change. >

 

Note A locally modified file that has not been reserved cannot be checked in.

Replacing and Adding
When you use the Check in (Replace) command to replace a file, its status returns to [Up-to-Date;<n>].

If you add a new file to a project that is under source control, it appears in the CMS Explorer as not being added to the CMS library ([Local] or [Locally Added]). You must explicitly add the file using the CMS command: Add (Create Element).

Form Files and Java Files

When using the NetBeans Form Editor, for every .form file there is a corresponding .java file. In such cases, you are reserving and replacing two files.


The form file is visible in the Explorer when it is open in the Form Editor

Usage Notes

If a Java file and its corresponding Form file are contained in the CMS library and no local copy exists (status is No Local Copy), the two files appear separately rather than as a single node. Before working on these files, you should reserve or fetch both the Java and Form files.
When a form file is up to date, the corresponding class or Java file is usually up to date also. However, it is possible for the status of the two files to be different. For example, [Up-to-Date, Locally Modified] would mean that the .java file code has been changed without affecting the form.

Status information in the Source Editor

The Source Editor shows the status of open files that are mounted in a CMS filesystem: