How to set up NetBeans with CloudForge

The Netbeans IDE has a builtin Subversion client which works with our service.


Before you start please make sure you have setup your Cloudforge account with at least 1 project, and added the Subversion service to that project. See here.

Once you have done this, locate your Subversion URL on your projects home page.


Checking your Project into Subversion

To check a pre-existing Netbeans project into your CloudForge repository you first need to right click on the project and then select Versioning -> Import into Subversion Repository.


After that you need to enter the URL you got when you created the project, and your username and password. You may also need to configure a proxy depending on your Internet connection.


Next you'll need to choose which directory in the CloudForge repository you want to import the files into, in this case I choose the trunk, but you might want to use a branch instead (Netbeans will create this directory), and type in a commit message (which will appear in the Subversion logs).


Finally you need to choose which files to commit. I chose to commit everything, but in some cases you might want each individual user to have their own version of some files. After you click finish here Netbeans will commit the files and it will be ready for your teammates to check out into their own Netbeans instance and for you to commit changes you make.


Checking a Subversion Project out

If one of your teammates has already committed a Netbeans project to a Subversion repository you can choose Team -> Subversion -> Checkout to create a local copy of the project.


After this you need to enter the Repository URL (which you can get from the project dashboard), username, and password.


You will also need to select which directory to checkout from the repository. Since we checked it into trunk earlier this is the directory we choose here. There are some additional options here that can be of use in some situations. A couple of options to note here:

  • The export a clean tree option will remove the Subversion hidden files from the local copy meaning that you can't commit changes and update the local copy then; this can be useful for rollouts. 
  • If you leave the scan for Netbeans projects option checked it will automatically create a new Netbeans project for you with the files you checkout.


Commits and Updates

After you've checked your repository out or added your project to Subversion you will have a new right click -> Subversion menu.


The two most useful of these functions are:

  • Update, which grabs the latest version on the CloudForge server and merges it into your local copy (without overwriting local changes).
  • Commit, which copies all your local changes to the CloudForge server.

All the others are useful on occasions as well, in particular "Show Changes", which lists all the files changed in your local copy, "Search History", which allows you to examine the previous commits, "Revert Modifications", which undos any local changes, and "Resolve Conflicts", which allows you to compare conflicting changes side by side and choose which to keep.



Article is closed for comments.