Skip to content

Latest commit

 

History

History
326 lines (221 loc) · 11.1 KB

README.md

File metadata and controls

326 lines (221 loc) · 11.1 KB
Raw

Developing Pressgang

If you want to build or contribute to a pressgang project, read this document.

This document will save you and us a lot of time by setting up your development environment correctly. It solves all known pitfalls that can disrupt your development. It also describes all guidelines, tips and tricks.

If you discover pitfalls, tips and tricks not described in this document, please update it using the markdown syntax.

Table of Contents

  • Building with Maven

  • Developing with Eclipse

  • Developing with IntelliJ

  • Team communication

  • Releasing

  • FAQ

Building with Maven

All projects use Maven 3 to build all their modules.

Downloading and Installing Maven

Note: The apt-get and yum versions of maven may not be up-to-date enough. Verify the version is current before installing (no more than two versions behind)

  1. Download Maven and follow the installation instructions.

  2. Unzip maven to ~/opt/build

  3. Create a version-independent link (on Linux):

     $ cd ~/opt/build/
 $ ln -s apache-maven-3.0.3 apache-maven

    Next time you only have to remove the link and add it to the new version.

  4. Add this to the ~/.bashrc file (on Linux):

     export M3_HOME="~/opt/build/apache-maven"
 export PATH="$M3_HOME/bin:$PATH"

  5. Allocate more memory to maven for building large projects.

    Linux: add the following line to the ~/.bashrc file

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

    Windows: Open menu Configuration > System > Advanced tab > Environment Variables button:

     set MAVEN_OPTS="-Xms256m -Xmx1024m -XX:MaxPermSize=512m"

  6. Check if maven is installed correctly.

     $ mvn --version
 Apache Maven 3.0.3 (...)
 Java version: 1.7.0

    Note: the Maven enforcer plugin enforces a minimum maven and java version.

Running the build

  1. Go into a project's base directory:

     $ cd ~/projects/pressgang-tools
 $ ls
 ...  pressgang-xslt pressgang-xslt-ns  pom.xml

    The pom.xml files are the heart of Maven, and control how the project is built.

  2. Run the build

     $ mvn clean install -DskipTests

    The first build will take a long time, because a lot of dependencies will be downloaded (and cached locally).

    It might even fail, if certain servers are offline or experience hiccups. In that case, you'll see an IO error, so just run the build again.

    After the first successful build, subsequent builds should be fast and stable.

Configuring Maven

To deploy snapshots and releases to nexus, you need to add the block to the ~/.m2/settings.xml file:

 <settings>
   ...
   <servers>
     <server>
       <id>jboss-snapshots-repository</id>
       <username>jboss.org_username</username>
       <password>jboss.org_password</password>
     </server>
     <server>
       <id>jboss-releases-repository</id>
       <username>jboss.org_username</username>
       <password>jboss.org_password</password>
     </server>
   </servers>
   ...
 </settings>

More info in the JBoss.org guide to get started with Maven.

Developing with Eclipse

Before running Eclipse

  • Do not use an Eclipse version older than 3.6 (helios).

Configuring the project with the m2eclipse plugin

The m2eclipse plugin is a plugin in Eclipse for Maven. This is the new way (and compatible with tycho).

  1. Open Eclipse

  2. Follow the installation instructions of m2eclipse.

    • Follow the link Installing m2eclipse at the bottom.

  3. Click menu File, menu item Import, tree item Maven, tree item Existing Maven Projects.

  4. Click button Browse, select a repository directory. For example ~/projects/pressgang-tools.

Configuring Eclipse

  1. Set the correct file encoding (UTF-8 except for properties files) and end-of-line characters (unix):

    • Open menu Window, menu item Preferences.
    • Click tree item General, tree item Workspace
    • Label Text file encoding, radiobutton Other, combobox UTF-8.
    • Label New text file delimiter, radiobutton Other, combobox Unix.
    • Click tree item XML, tree item XML Files.
    • Combobox Encoding: ISO 10646/Unicode(UTF-8).
    • Click tree item CSS, tree item CSS Files.
    • Combobox Encoding: ISO 10646/Unicode(UTF-8).
    • Open tree item HTML, tree item HTML Files.
    • Combobox Encoding: ISO 10646/Unicode(UTF-8).

    Note: normal i18n properties files must be in ISO-8859-1 as specified by the java ResourceBundle contract. GWT i18n properties files override that and must be in UTF-8 as specified by the GWT contract.

  2. Set the correct number of spaces when pressing tab: Warning: If you imported the eclipse-formatter.xml file, you don't need to set it for Java, but you do need to set it for XML anyway!

    • Open menu Window, menu item Preferences.
    • If you have project specific settings enabled instead, right click on the project and click the menu item Properties.
    • Click tree item Java, tree item Code Style, tree item Formatter.
    • Click button Edit of the active profile, tab Indentation
    • Combobox Tab policy: spaces only
    • Textfield Indentation size: 4
    • Textfield Tab size: 4 Note: If it is a build-in profile, you 'll need to change its name with the textfield on top.
    • Click tree item XML, tree item XML Files, tree item Editor.
      • Radiobutton Indent using space: on
      • Textfield Indentation size: 2
    • Click tree item General, tree item Editors, tree item Text Editors.
      • Checkbox Insert spaces for tabs: on
      • Textfield Displayed tab width: 4
    • Click tree item CSS Files, tree item Editor.
      • Radiobutton Indent using space: on
      • Textfield Indentation size: 4

Developing with IntelliJ

Configuring the project with the maven integration

IntelliJ has very good build-in support for Maven.

  1. Open IntelliJ.

  2. Import the pressgang-tools module

    • Click menu File, menu item Import Module.
    • Click radiobutton Create project from scratch, button Next
    • Textfield name: pressgang-tools
    • Textfield Project files location: ~/projects/pressgang-tools
    • Checkbox Create module: off

  3. Click menu File, menu item New module

  4. Click the pressgang-tools git repo root (where the pom.xml file resides) and click OK.

  5. Select Import from external model radio button, select Maven, and then click Next.

  6. In the Import Module screen, make the following changes

    • Textfield Root directory: ~/projects/pressgang-tools (or where you cloned the pressgang-tools GIT repo) That is the directory that contains the multiproject pom.xml file from a project base directory.

  7. Verify the maven projects to import (there should be one called org.jboss.pressgang:pressgang-tools[VERSION]) and click Next.

  8. Click Next to move past the SDK screen.

  9. Click Finish.

  10. Go grab a coffee while it's indexing. ;)

Configuring IntelliJ

  1. Avoid that changes in some resources are ignored in the next run/debug (and you are forced to use mvn)

    • Open menu File, menu item Settings
    • Click tree item Compiler, textfield Resource patterns:
    • change to !?*.java (remove other content)

  2. Set the correct file encoding (UTF-8 except for properties files) and end-of-line characters (unix):

    • Open menu File, menu item Settings
    • Click tree item Code Style, tree item General
      • Combobox Line separator (for new files): Unix
    • Click tree item File Encodings
      • Combobox IDE Encoding: UTF-8
      • Combobox Default encoding for properties files: ISO-8859-1 Note: normal i18n properties files must be in ISO-8859-1 as specified by the java ResourceBundle contract. GWT i18n properties files override that and must be in UTF-8 as specified by the GWT contract.

  3. Set the correct number of spaces when pressing tab:

    • Open menu File, menu item Settings
    • Click tree item Code Style, tree item General
    • Click tab Java
      • Checkbox Use tab character: off
      • Textfield Tab size: 4
      • Textfield Indent: 4
      • Textfield Continuation indent: 8
    • Open tab XML
      • Checkbox Use tab character: off
      • Textfield Tab size: 2
      • Textfield Indent: 2
      • Textfield Continuation indent: 4

Team communication

To develop a great project as a team, we need to communicate efficiently as a team.

Subscribe to the RSS feeds

It is recommended you subscribe to the RSS feeds of the project/repostories you are working on.

Choose a RSS reader which shows which RSS articles you've already read, such as:

Thunderbird:

  1. Open menu File,
  2. Menu item Subscribe.
  3. Create a new, separate directory for each feed.

NOTE: Some feeds (such as about the project you are working on) are more important to you than others.

Zimbra:

http://blog.zimbra.com/blog/archives/2007/05/zimbras-built-in-rssatom-feed-reader.html

Subscribe to jira issue changes

https://issues.jboss.org/plugins/servlet/streams?key=JDOCBOOKSTYLE&os_authType=basic

Join us on IRC

irc.freenode.net #PressGang

Releasing

NEVER TAG OR DEPLOY A VERSION THAT ALREADY EXISTS AS A TAG OR A DEPLOY!!!

* Except deploying `SNAPSHOT` versions.
* Git tags are cached on developer machines forever and are never refreshed.
* Maven non-snapshot versions are cached on developer machines and proxies forever and are never refreshed.
* So even if the release is broken, do not reuse the same version number! Create a hotfix version.

  1. First check it builds:

       $ mvn clean install -Dfull

    The -Dfull will also build pressgang-tools-example (which can't be build during the release due to a catch 22). Do a quick sanity check on the html and pdf output of that example.

  2. If everything is perfect, define the version and create the tag:

     $ mvn release:prepare

    Note: Always use at least 3 numbers in the version: '2.0.0' is fine, 2.0 is not fine.

  3. Deploy the artifacts:

     $ mvn release:perform

    Afterwards manually upgrade the pressgang-tools-example parent version number.

  4. Go to nexus, menu item Staging repositories, find your staging repository.

    • Button close
    • Button release

  5. Go to jira:

    • Open menu item Administration, link Manage versions, release the version.
    • Create new versions if needed. Warning: The slightest change after you created the tag requires the use of the next version number!

FAQ