Permalink
Switch branches/tags
hornetq_2_0_0_CR1 Hornetq_2_1_1_Final Hornetq_2_1_0_Final Hornetq_2_1_0_CR1 HornetQ_2_5_0_Beta1 HornetQ_2_4_7_Final HornetQ_2_4_6_Final HornetQ_2_4_5_Final HornetQ_2_4_4_Final HornetQ_2_4_3_Final HornetQ_2_4_2_Final HornetQ_2_4_1_Final HornetQ_2_4_0_Final HornetQ_2_4_0_Beta3 HornetQ_2_4_0_Beta2 HornetQ_2_4_0_Beta1 HornetQ_2_4_0_Alpha1 HornetQ_2_3_25_SP24 HornetQ_2_3_25_SP23 HornetQ_2_3_25_SP22 HornetQ_2_3_25_SP21 HornetQ_2_3_25_SP20 HornetQ_2_3_25_SP19 HornetQ_2_3_25_SP18 HornetQ_2_3_25_SP17 HornetQ_2_3_25_SP16 HornetQ_2_3_25_SP15 HornetQ_2_3_25_SP14 HornetQ_2_3_25_SP13 HornetQ_2_3_25_SP12 HornetQ_2_3_25_SP11 HornetQ_2_3_25_SP10 HornetQ_2_3_25_SP9 HornetQ_2_3_25_SP8 HornetQ_2_3_25_SP7 HornetQ_2_3_25_SP6 HornetQ_2_3_25_SP5 HornetQ_2_3_25_SP4 HornetQ_2_3_25_SP3 HornetQ_2_3_25_SP2 HornetQ_2_3_25_SP1 HornetQ_2_3_25_Final HornetQ_2_3_24_Final HornetQ_2_3_23_Final HornetQ_2_3_22_Final HornetQ_2_3_21_2_Final HornetQ_2_3_21_1_Final HornetQ_2_3_21_Final HornetQ_2_3_20_Final HornetQ_2_3_19_Final HornetQ_2_3_18_Final HornetQ_2_3_17_Final HornetQ_2_3_16_Final HornetQ_2_3_15_Final HornetQ_2_3_14_1_Final HornetQ_2_3_14_Final HornetQ_2_3_13_Final HornetQ_2_3_12_Final HornetQ_2_3_11_Final HornetQ_2_3_10_Final HornetQ_2_3_9_Final HornetQ_2_3_8_Final HornetQ_2_3_7_Final HornetQ_2_3_6_Final HornetQ_2_3_5_1_Final HornetQ_2_3_5_Final HornetQ_2_3_4_Final HornetQ_2_3_3_FINAL HornetQ_2_3_2_FINAL HornetQ_2_3_1_FINAL HornetQ_2_3_0_FINAL HornetQ_2_3_0_CR2 HornetQ_2_3_0_CR1 HornetQ_2_3_0_Beta3 HornetQ_2_3_0_Beta2 HornetQ_2_3_0_Beta1 HornetQ_2_3_0_Alpha HornetQ_2_2_30_Final HornetQ_2_2_29_Final HornetQ_2_2_28_Final HornetQ_2_2_27_Final HornetQ_2_2_26_Final HornetQ_2_2_25_Final HornetQ_2_2_24_EAP_GA HornetQ_2_2_23_AS7_Final HornetQ_2_2_22_AS7_Final HornetQ_2_2_21_AS7_Final HornetQ_2_2_20_EAP_GA HornetQ_2_2_20_EAP_GA_build2 HornetQ_2_2_19_AS7_Final HornetQ_2_2_19_AS7_Final_build2 HornetQ_2_2_18_AS7_Final HornetQ_2_2_17_AS7_Final HornetQ_2_2_16_AS7_Final HornetQ_2_2_15_AS7_Final HornetQ_2_2_14_Final HornetQ_2_2_13_AS7_Final HornetQ_2_2_12_AS7_Final HornetQ_2_2_11_EAP_GA HornetQ_2_2_11_AS7_Final
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
162 lines (98 sloc) 5.13 KB

HornetQ

If you need information about the HornetQ project please go to

http://community.jboss.org/wiki/HornetQ

http://www.jboss.org/hornetq/

This file describes some minimum 'stuff one needs to know' to get started coding in this project.

Source

The project's source code is hosted at:

https://github.com/hornetq

Git usage:

Pull requests should be merged without fast forwards '--no-ff'. An easy way to achieve that is to use

% git config branch.master.mergeoptions --no-ff

Maven

The minimum required Maven version is 3.0.0.

Do note that there are some compatibility issues with Maven 3.X still unsolved 1. This is specially true for the 'site' plugin 2.

Tests

To run the unit tests:

% mvn -Phudson-tests test

Generating reports from unit tests:

% mvn install site

Running tests individually

% mvn -Phudson-tests -DfailIfNoTests=false -Dtest=<test-name> test

where <test-name> is the name of the Test class without its package name

Examples

To run an example firstly make sure you have run

% mvn -Prelease install

If the project version has already been released then this is unnecessary.

then you will need to set the following maven options, on Linux by

export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"

and the finally run the examples by

% mvn verify

You can also run individual examples by running the same command from the directory of which ever example you want to run. NB for this make sure you have installed examples/common.

Recreating the examples

If you are trying to copy the examples somewhere else and modifying them. Consider asking Maven to explicitly list all the dependencies:

# if trying to modify the 'topic' example:
cd examples/jms/topic && mvn dependency:list

To build a release artifact

% mvn -Prelease install

To build the release bundle

% mvn -Prelease package

Eclipse

We recommend using Eclipse Indigo (3.7) or Eclipse Juno (4.2), due to the built-in support for Maven and Git. Note that there are still some Maven plugins used by sub-projects (e.g. documentation) which are not supported even in Eclipse Juno (4.2).

Eclipse m2e is already included in "Eclipse IDE for Java Developers", or it can be installed from Eclipse Juno release repository.

Annotation Pre-Processing

HornetQ uses JBoss Logging and that requires source code generation from Java annotations. In order for it to 'just work' in Eclipse you need to install the Maven Integration for Eclipse JDT Annotation Processor Toolkit m2e-apt. See this JBoss blog post for details.

M2E Connector for Javacc-Maven-Plugin

Eclipse Indigo (3.7) has out-of-the-box support for it.

As of this writing, Eclipse Juno (4.2) still lacks support for Maven's javacc plugin. See this post on the m2e connector for javacc-maven-plugin for manual installation instructions (as of this writing you need to use the development update site).

Use Project Working Sets

Importing all HornetQ subprojects will create too many projects in Eclipse, cluttering your Package Explorer and Project Explorer views. One way to address that is to use Eclipse's Working Sets feature. A good introduction to it can be found at a Dzone article on Eclipse Working Sets.

Code Formatting

Eclipse code formatting and (basic) project configuration files can be found at the etc/ folder. You should manually copy them after importing all your projects:

for settings_dir in `find . -type d -name .settings`; do
   \cp -v etc/org.eclipse.jdt.* $settings_dir
done

Do not use the maven-eclipse-plugin to copy the files as it conflicts with m2e.

Github procedures

HornetQ accepts contributions through pull requests on GitHub. After review a pull request should either get merged or be rejected.

When a pull request needs to be reworked, say you have missed something, the pull request is then closed, at the time you finished the required changes you should reopen your original Pull Request and it will then be re-evaluated. At that point if the request is aproved we will then merge it.

Make sure you always rebase your branch on master before submitting pull requests.