Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SWTBot/Maintaining SWTBot Versions For Your Team"
(Initial content) |
m (removed some manual steps that are now automated) |
||
| Line 5: | Line 5: | ||
SWTBot comes with a releng project and things generally work out of the box. See the {{SWTBotLink|Contributing| Contributing}} for how to build SWTBot. | SWTBot comes with a releng project and things generally work out of the box. See the {{SWTBotLink|Contributing| Contributing}} for how to build SWTBot. | ||
| − | ===Installation from the | + | ===Installation from the Source Repository=== |
If you expect to be making changes to the SWTBot source code then the you should consider using GIT. The SWTBot Subversion repository is mirrored to a GIT repository. Although GIT has a higher learning curve than Subversion, you will find it easier to manage your changes and it will be easier for others to pull your changes. | If you expect to be making changes to the SWTBot source code then the you should consider using GIT. The SWTBot Subversion repository is mirrored to a GIT repository. Although GIT has a higher learning curve than Subversion, you will find it easier to manage your changes and it will be easier for others to pull your changes. | ||
| Line 11: | Line 11: | ||
The GIT repository is at git://github.com/ketan/swtbot.git. | The GIT repository is at git://github.com/ketan/swtbot.git. | ||
| − | + | If you clone this repository and import the projects into Eclipse, you will find a few errors. These can be fixed by running the ant targets '''materialize-workspace'''. See the readme file in the releng plugin for more. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
===Building an SWTBot Update Site=== | ===Building an SWTBot Update Site=== | ||
Latest revision as of 03:15, 1 July 2009
| SWTBot |
| Website |
| Update Sites |
| Community |
| Mailing List |
| Forums/Newsgroups |
| IRC |
| Contribute |
| Open Bugzilla tickets |
| Open Gerrit reviews |
| Browse Source |
| Continuous Integration |
Building SWTBot From Source
SWTBot comes with a releng project and things generally work out of the box. See the Contributing for how to build SWTBot.
Installation from the Source Repository
If you expect to be making changes to the SWTBot source code then the you should consider using GIT. The SWTBot Subversion repository is mirrored to a GIT repository. Although GIT has a higher learning curve than Subversion, you will find it easier to manage your changes and it will be easier for others to pull your changes.
The GIT repository is at git://github.com/ketan/swtbot.git.
If you clone this repository and import the projects into Eclipse, you will find a few errors. These can be fixed by running the ant targets materialize-workspace. See the readme file in the releng plugin for more.
Building an SWTBot Update Site
If you are using SWTBot in a project with many developers, and you want those other developers to run and maintain test, and you have made modifications to SWTBot then you will want to make those modifications easily available to the other developers. The easiest way to do this is to set up an update site that contains SWTBot with your modifications.
To create an update site, follow the instructions in MakingARelease.HOWTO in the org.eclipse.swtbot.releng bundle. Do not use the org.eclipse.swtbot.updatesite bundle. That is old stuff that creates an old-style update site (it predates Equinox p2). You should ensure unique versions, generally done by including your company name or project name in the version string.
The build.xml file contains the script for building the update site. However you must first ensure you have all the dependencies. A separate script is provided to install the dependencies. This script requires eclipse.sdk.url and eclipse.sdk.archive properties to be set to the location and name of the Eclipse SDK archive file. The best way to be sure you have all the properties set is to copy build.developer.properties.sample to build.developer.properties and edit as appropriate.
Once those are set, you can install the dependencies by running:
ant -file download-dependencies.xml download-dependencies
or just run the build.xml script which will run tasks in this script if necessary.
You will need 'unzip' on the command path. If you are running Windows then you can download a compatible unzip implementation from http://gnuwin32.sourceforge.net/packages/unzip.htm.