-
Notifications
You must be signed in to change notification settings - Fork 3
Developers
This page is intended for developers of the BEL Editor.
-
Clone the fork
git clone ... -
Checkout the unstable branch
git checkout unstable -
Add the main repository
git remote add main_repo [email protected]:OpenBEL/bel-editor.git -
Push to the main repository when you have changes
git push main_repo unstable
The BEL Editor is hosted on GitHub.
The main repository consists of two branches, stable and unstable.
The two branches mirror the
stable and unstable Eclipse repositories.
The stable branch contains the latest stable release of the BEL Editor, suitable
for daily use. The unstable branch contains experimental code that is only
suitable for testing and experimenting with new features.
Developers should work in forks of the main repository.
-
Any branching strategy is fine for a fork.
Examples: (1) using feature branches, (2) bug branches, and (3) using the
unstablebranch -
New code should be merged into the
unstablebranch of your fork. -
If a feature or bug is suitable for testing, push the fork's
unstablebranch to the main repository. -
The
stablebranch in the main repository is only ever updated with code merged fromunstable.
Issue tracking is done through our GitHub issue tracker.
The BEL Editor is built automatically when the main repository is pushed to. An instance of Atlassian Bamboo manages all builds of OpenBEL software. Deployments of the BEL Editor to the Eclipse repositories are also managed by Bamboo.
The BEL Editor consists primarily of two plugins:
-
org.openbel.editor.core: Parts of the BEL language, parsing, and organizing projects. -
org.openbel.editor.ui: User interface components for editing BEL and organizing projects.
The local-repo script allows you
to host a local P2 repository
to install
the development version (the current working tree) into Eclipse.
Committers to the BEL Editor are eligible for a license of JRebel which is well-suited for developing Eclipse plugins.
TODO