JBoss Tools :: JavaEE { batch, cdi, jsf, seam, struts }
Java HTML CSS Roff JavaScript XSLT
Switch branches/tags
soatools-3.3.0.GA jbosstools-4.5.3.Final jbosstools-4.5.3.AM3 jbosstools-4.5.3.AM2 jbosstools-4.5.3.AM1 jbosstools-4.5.2.Final jbosstools-4.5.2.AM2 jbosstools-4.5.2.AM1 jbosstools-4.5.1.Final jbosstools-4.5.1.AM3 jbosstools-4.5.1.AM2 jbosstools-4.5.1.AM1 jbosstools-4.5.0.Final jbosstools-4.5.0.AM2 jbosstools-4.5.0.AM1 jbosstools-4.4.4.Final jbosstools-4.4.4.AM3 jbosstools-4.4.4.AM2 jbosstools-4.4.4.AM1 jbosstools-4.4.3.Final jbosstools-4.4.3.AM2 jbosstools-4.4.3.AM1 jbosstools-4.4.2.Final jbosstools-4.4.2.AM3 jbosstools-4.4.2.AM2 jbosstools-4.4.2.AM1 jbosstools-4.4.1.Final jbosstools-4.4.1.AM3 jbosstools-4.4.0.Final jbosstools-4.4.0.Alpha2 jbosstools-4.3.1.Final jbosstools-4.3.1.Beta2 jbosstools-4.3.1.Beta1 jbosstools-4.3.0.Final jbosstools-4.3.0.CR1 jbosstools-4.3.0.Beta2 jbosstools-4.3.0.Beta1 jbosstools-4.3.0.Alpha2 jbosstools-4.3.0.Alpha1 jbosstools-4.2.3.Final jbosstools-4.2.3.CR1 jbosstools-4.2.3.Beta1 jbosstools-4.2.2.Final jbosstools-4.2.1.Final jbosstools-4.2.0.Final jbosstools-4.2.0.CR1 jbosstools-4.2.0.Beta3 jbosstools-4.2.0.Beta2 jbosstools-4.2.0.Beta1 jbosstools-4.2.0.Alpha2 jbosstools-4.2.0.Alpha1 jbosstools-4.1.2.Final jbosstools-4.1.1.Final jbosstools-4.1.1.CR1 jbosstools-4.1.1.Beta1 jbosstools-4.1.0.Final jbosstools-4.1.0.Beta1 jbosstools-4.0.0.Final jbosstools-4.0.0.Alpha2 jbosstools-4.0.0.Alpha1 jbosstools-3.3.1.Final jbosstools-3.3.0.Final jbosstools-3.2.2.Final jbosstools-3.2.1.Final jbosstools-3.2.0.Final jbosstools-3.1.1.GA jbosstools-3.1.0.GA jbosstools-3.0.3.GA jbosstools-3.0.2.GA jbosstools-3.0.1.GA jbosstools-3.0.0.GA jbosstools-2.1.2.GA jbosstools-2.1.1.GA jbosstools-2.1.0.GA jbosstools-2.0.1.GA jbosstools-2.0.0.GA
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
all-tests [JBIDE-23642] Bump version for 4.4.3 / 10.3.0 (#421) Dec 14, 2016
batch bump batch plugins/features versions to make baseline checker happy Dec 21, 2017
cdi
jsf [JBIDE-25965] - Adapt javaee for Photon Apr 20, 2018
seam [JBIDE-25965] - Adapt javaee for Photon (#452) Apr 23, 2018
site
.gitignore JBIDE-12951 add bin and target to all root .gitignores Oct 26, 2012
README.md JBDS-4495 update readmes - Seam 3 != CDI, so CDI is not deprecated yet Aug 8, 2017
pom.xml

README.md

The JavaEE Tools project

Summary

JavaEE Tools provides Eclipse plugins for features related to development on JavaEE. This includes Batch, JSF & struts.

Seam 2 & Seam 3 (org.jboss.tools.cdi.seam.feature) are deprecated as of JBoss Tools 4.5.0.

Install

JavaEE Tools is part of JBoss Tools from which it can be downloaded and installed on its own or together with the full JBoss Tools distribution.

Get the code

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

$ git clone git@github.com:<you>/jbosstools-javaee.git
$ cd jbosstools-javaee
$ git remote add upstream git://github.com/jbosstools/jbosstools-javaee.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'.

Building JavaEE Tools

To build JavaEE Tools requires specific versions ofJava (1.6+) and +Maven (3.1+). See this link 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

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

Contribute fixes and features

JavaEE Tools is open source, and we welcome anybody that wants to participate and contribute!

If you want to fix a bug or make any changes, please log an issue in the JBoss Tools JIRA describing the bug or new feature and give it a component type of cdi, seam, struts or jsf. Then we highly recommend making the changes on a topic branch named with the JIRA issue number. For example, this command 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 unit tests) runs successfully, commit your changes on your topic branch (with good comments). Then it's time to check for any recent changes that 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 with tests 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 JavaEE Tools

And then generate a pull-request where we can review the proposed changes, comment on them, discuss them with you, and if everything is good merge the changes right into the official repository.