Azureus CVS

From VuzeWiki
Jump to: navigation, search

What is CVS?[edit]

CVS (Concurrent Versions System) is a tool used by many software developers to manage changes within their source code tree. CVS provides the means to store not only the current version of a piece of source code, but a record of all changes (and who made those changes) that have occurred to that source code. Use of CVS is particularly common on projects with multiple developers, since CVS ensures changes made by one developer are not accidentally removed when another developer posts their changes to the source tree.

Vuze/Azureus used the Sourceforge CVS server until April 2010, when it changed to use an own SVN server for the version control. Currently the Vuze source code can be found from .

  • SVN or formally Subversion is a newer CVS system, which is meant to be a successor for the old traditional CVS.
  • Information about downloading and compiling the source code can be found e.g. from the Using Eclipse article.

Every day or so a snapshot is taken of the Vuze code in the SVN repository. That snapshot is compiled into a .jar (java zip) file, which can then replace the one you are currently using. Think of it as a daily beta for developers. Beta versions often include many features, changes, and bug-fixes added since the last release version. But they can also often include bugs and less tested code and therefore be less stable than the release versions. Beta versions generally exist so various volunteers can test changes in the code and shake out the bugs, report errors, and help optimize the code for the next official release.

  • Information, useful links and beta versions targeted for developers/testers can be found from:
  • The beta .jar files are titled AzureusVVVV-Bxx.jar where VVVV is the current main version and xx is the current build number since the last release.

How to install the latest Beta build of Vuze[edit]

Installing stable Beta versions automatically[edit]

Join the Beta Program for the simplest way to get relatively stable beta versions.

Installing the latest Beta .jar manually[edit]

Caution: The latest Developer beta builds have no guarantee of stability and contain code that might be untested. You use them at your own risk. While there rarely is a severe problem with the beta versions, make sure you're backing up your user information and config settings before using a developer beta build. Note: when you decide to use the betas you should update it again at least weekly, since there are always changes being made and if you run into problems that could have already been fixed in a new beta version.

(If you're on a Mac, there are Mac OS X specific instructions available here: Change the Azureus2.jar file)

  • Close your Vuze client completely
  • Download the latest AzureusVVVV-Bxx.jar file from
  • Do not try to extract it, just rename the .jar file to Azureus2.jar (remove the VVVV-Bxx part; note that you don't see the .jar if your Windows is configured to hide the known file-extensions!)
  • Move the .jar file to your Vuze program directory, overwriting the one currently there (it is recommended you back up the previous .jar file in case the new version causes problems - make sure you rename the "jar" extension of the previous file to something else)
  • Start Vuze - you should now see the new version number in the bottom left of the window.
  • Go to Vuze > Help > Check for Updates - if there are any, install them and restart Vuze (also install any "Automatic Updates" Vuze suggests to download)

That's it.


Thanks to some great work by Omschaub, there's a plugin that automates the developer beta jar file updating process. You can find it on the plugin page here:

The original name of the plugin was AZCVSUpdater, but its currently displayed name is Vuze Beta updater.

Some of the features of this plugin include

  • Automatic beta version checking and optional auto-downloading
  • Optional Automatic restarting
  • Automatic backup of previous CVS versions
  • The ability to easily switch to any previously downloaded and stored beta build
  • Simple beta build management including the ability to add comments to any particular build

For updates and questions, please visit the Plugins section of Vuze forum:

How to install the Azureus Beta using AZCVSUpdater[edit]

1. Get the AZCVSUpdater / Vuze Beta Updater plugin.

  • Start Vuze, and go to the Plugins menu. If 'AZCVSUpdater' or 'Vuze Beta Updater' is listed, skip to step 2.
  • Pick Installation Wizard. The radio button for By list from should be selected. Pick Next>.
  • Put a check in the box next to the AZCVSUpdater plugin. Pick Next>.
  • Choose whether to install the plugin for all users, or only for yourself. The default is all users. Pick Finish.
  • A new window will appear showing what plugins were selected, and their version and size. Pick the Install button. It should only take a minute or so for the plugin to download and install, at which time you can pick Close to close the plugin installer window.

2. Go to the Plugins menu, and choose the AZCVSUpdater or Vuze Beta Updater.

3. On the 'Dev Beta Update' tab's Information page, you will see the latest version information. If you do not, pick the refresh button to the right. The information shown here updates automatically every 160 minutes.


4. Compare the latest Developer beta version available to the current version you have installed. If the beta is newer, you can download and install it. If not, check back here each day and review the latest version information again.

5. If there is a new version, you can download it by clicking the manual download button to the right. This starts a torrent in Vuze, and it should only take a few minutes to finish. Once it is done downloading you can proceed to install it.

Note: You can configure the plugin to automatically check and download new developer beta versions.

6. To install the latest beta of Vuze, go to the AZCVSUpdater plugin, and the 'Insert Beta File' tab. Pick Yes for 'Would you like to insert a backup file as Azureus2.jar?'. In the pulldown, choose the beta version you want to install.

7. Click Submit. Then choose whether to accept and restart now, later or exit. Depending on your choice, Vuze will either restart with the new beta, or put the beta in place but not restart, requiring you to restart Vuze manually, or simply exit, and the new CVS will be in place for the next time you start Vuze.

8. Once Vuze is restarted, the new beta version should be displayed in the lower left corner of Vuze.

You can then repeat this process when a new beta comes out. There are also options in the AZCVSUpdater to automatically download, install and restart Vuze when a new release is discovered. However, if you're unsure about letting Vuze do it automatically, it's best to do it by hand when you can afford to deal with a problem the latest release may cause. Vuze beta releases are usually very stable and rarely cause problems, although it is possible.

Reporting bugs in beta versions[edit]

Register and post it in the Vuze Forums: Bug Reports forum.

Please include your CVS build version in the subject line. Make sure you use the latest beta before reporting a bug! Before posting, try to isolate the problem as much as possible. See if the bug exists in older builds or if it's something new and include that information. Be as detailed as you can and include instructions others can use to attempt to reproduce the bug on their systems in order to confirm it. And finally, check the forums and the wiki first to see if anyone else has already posted about it.

How can I tell what's changed from snapshot to snapshot?[edit]

There is no easy way to tell, however, you can get subscribe to the commitlog mailing list and get e-mails every time a developer changes something in the code. Usually there's a comment on what they are trying to fix, or what they are doing. The mailing list is at and is called "azureus-commitlog Archives". You can also browse past commitlogs from that page.

Back to Tips and Tricks

Read the Azureus FAQ