Repository files navigation

JBoss Tools Base contains set of base plugins used in many JBoss Tools Eclipse plugins.

JBoss Tools Base is part ofJBoss Tools fromwhich it can bedownloaded and installedon its own or together with the full JBoss Tools distribution.

The easiest way to get started with the code is tocreate your own fork,and then clone your fork:

$ git clone git@github.com:<you>/jbosstools-base.git$ cd jbosstools-base$ git remote add upstream git://github.com/jbosstools/jbosstools-base.git

At any time, you can pull changes from the upstream and merge them onto your master:

$ git checkout master               # switches to the 'master' branch$ git pull upstream master          # fetches all 'upstream' changes and merges 'upstream/master' onto your 'master' branch$ git push origin                   # pushes all the updates to your fork, which should be in-sync with 'upstream'

The general idea is to keep your 'master' branch in-sync with the'upstream/master'.

To buildJBoss Tools Base requires specific versions of Java (1.6+) and+Maven (3.1+). See thislink for more information on how to setup, run and configure build.

This command will run the build:

$ mvn clean verify

If you just want to check if things compiles/builds you can run:

$ mvn clean verify -DskipTest=true

Butdo not push changes without having the new and existing unit tests pass!

JBoss Tools Base is open source, and we welcome anybody that wants toparticipate and contribute!

If you want to fix a bug or make any changes, please log an issue intheJBoss Tools JIRAdescribing the bug or new feature and give it a component type ofcommon/jst/core, runtime detection or usage. Then we highly recommend making the changes on atopic branch named with the JIRA issue number. For example, thiscommand creates a branch for the JBIDE-1234 issue:

$ git checkout -b jbide-1234

After you're happy with your changes and a full build (with unittests) runs successfully, commit your changes on your topic branch(with good comments). Then it's time to check for any recent changesthat were made in the official repository:

$ git checkout master               # switches to the 'master' branch$ git pull upstream master          # fetches all 'upstream' changes and merges 'upstream/master' onto your 'master' branch$ git checkout jbide-1234           # switches to your topic branch$ git rebase master                 # reapplies your changes on top of the latest in master                                      (i.e., the latest from master will be the new base for your changes)

If the pull grabbed a lot of changes, you should rerun your build withtests enabled to make sure your changes are still good.

You can then push your topic branch and its changes into your public fork repository:

$ git push origin jbide-1234         # pushes your topic branch into your public fork of JBoss Tools Base

And thengenerate a pull-request where we canreview the proposed changes, comment on them, discuss them with you,and if everything is good merge the changes right into the officialrepository.