Difference between revisions of "CVS Development"

Revision as of 15:07, 19 January 2007

Plug-ins

The CVS component contains the following plugins:

• org.eclipse.team.cvs.core
• org.eclipse.team.cvs.ui
• org.eclipse.team.cvs.ssh
• org.eclipse.team.cvs.ssh2
• org.eclipse.team.tests.cvs.core

It also consists of a feature project

• org.eclipse.cvs-feature

There is also a CVS mailing list

• platform-cvs-dev@eclipse.org (post, archives)

Bugzilla

Here's how to find bugs:

• New bugs that require triage have a

Status of New or Reopened and are assigned to platform-cvs-inbox@eclipse.org

• Bugs for which help is appreciated are marked with the helpwanted keyword

• Bugs that are targeted for a particular release of milestones are tagged with that milestone.

• Once triaged, Bugs are categorized in the following manner using the bracketed category identifier as a Summary prefix:
  • [Actions] - bugs that deal with CVS actions.
  • [Annotate View] - bugs that deal with the Annotate View
  • [Change Sets] - bugs that deal with Change Sets.
  • [Commands] - bugs that deal with the CVS command infrastrucutre.
  • [Connection] - bugs that deal with connecting to CVS
  • [Console View] - bugs that deal with the Console View.
  • [Decorators] - bugs that deal with CVS decorators.
  • [History] - bugs that deal with the CVS implementation of the History API
  • [History View] - bugs that deal with the CVS implementation of the History View page
  • [Misc] - bugs that defy categorization.
  • [Model Support] - bugs that deal with the model API
  • [Modules] - bugs that deal with CVS Modules
  • [Operations] - bugs that deal with CVS operations.
  • [Patch] - bugs that deal with Patching
  • [Preferences] - bugs that deal with the CVS preference page
  • [Repo View] - bugs that deal with the Repo View.
  • [Resources] - bugs that deal with CVS Resource
  • [Subscriber] - bugs that deal with the Subscriber API
  • [Sync Info] - bugs that deal with the Sync info infrastrcuture
  • [Sync View] - bugs that deal with the Sync View
  • [Tags] - bugs that deal with Tags
  • [Tests] - bugs that deal with CVS JUnit tests
  • [Watch/Edit] - bugs that deal with the Watch/Edit feature
  • [Wizards] - bugs that deal with the CVS Wizards

Running the CVS Automated Tests using JUnit

Follow these steps to run the CVS tests:

1. To load the Team/CVS test plug-ins, check out the following plug-ins from :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse repository:
   • org.eclipse.test
   • org.eclipse.test.performance
   • org.eclipse.core.tests.harness
   • org.eclipse.core.tests.resources
   • org.eclipse.team.tests.core
   • org.eclipse.team.tests.cvs.core
2. The CVS tests require a repository to test with so you will need to set up a test repository.
   • You can obtain the Linux flavour of CVS from here.
   • You can obtain the Windows flavour of CVS from here. Please refer to the this wiki entry on configuring CVSNT to work with Eclipse.
3. The org.eclipse.team.tests.cvs.core contains a couple of sample launch configurations:
   • CVS UI Tests: runs the tests related to the CVS/UI plug-in configured for windows
   • CVS UI Tests (Linux): same as above but configured for Linux
   • CVS Core Tests: runs the tests related to the CVS/Core plug-in
4. The Windows configuration is set up to use C:\eclipse as the test area. To configure the tests to use your test repository, perform the following steps:
   • copy the repository.properties file from the org.eclipse.team.tests.cvs.core plug-in to the C:\eclipse.
   • Open the file and modify the repository property to contain the location string that identifies your test repository. This string should be of the format :method:user:password@host:/repo/path (the other fields are used to tailor the tests in other ways but the defaults should work fine).
5. From the Run menu, choose Run.. and then select CVS UI Tests to run the tests.