JBoss Tools :: Aerogear { cordova, cordovasim, feedhenry }
JavaScript Java HTML
Switch branches/tags
Permalink
Failed to load latest commit information.
all-tests
cordova because 1.4.4 is in 4.4.x branch, must be 1.4.100 in master Apr 19, 2017
cordovasim
feedhenry JBIDE-23944: Prepare for 4.5.0.AM1 / 11.0.0.AM1 [aerogear-hybrid] Feb 27, 2017
site
.gitignore Initial code release Mar 4, 2013
README.md Fix upstream URL Jan 13, 2015
pom.xml JBIDE-24683 #comment bump up to parent pom version = 4.5.0.Final-SNAP… Jul 18, 2017

README.md

The JBoss Aerogear Tools Project

Summary

JBoss Aerogear Tools contains tools for cross-platform mobile development.

Currently the work is concentrated on providing Apache Cordova tools for hybrid mobile application development. Cordova tools provide Eclipse based tools for easing the development of Apache Cordova based hybrid mobile applications by hiding the complexities of multi-platform development and Cordova framewok.

Install

Releases are yet to come! But you can get the nightly builds from staging p2 update site

http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_master/all/repo/

Requirements

  • iOS SDK with the latest Xcode including the Xcode Command Line Tools
  • Android SDK with the absolute latest updates for all Android SDK components.

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

Building JBoss Cordova tools requires specific versions of Java (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

JBoss Cordova 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 aerogear-hybrid. 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 JBoss Central

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.