If you’re looking for a development guide for Forge 2.0, first read this document.
To contribute to Forge, fork the core repository to your own Git, clone your fork, commit your work on topic branches, and make pull requests.
If you don’t have the Git client (git), get it from: http://git-scm.com/
Here are the steps in detail:
-
Fork the project. This creates a the project in your own Git with the default remote name 'origin'.
-
Clone your fork. This creates and populates a directory in your local file system.
git clone git@github.com:<your-username>/core.git
-
Add the remote
upstreamrepository so you can fetch any changes to the original forked repository.git remote add upstream git@github.com:forge/core.git
-
Get the latest files from the
upstreamrepository.git fetch upstream
-
Create a new topic branch to contain your features, changes, or fixes using the
git checkout -b <topic-branch-name> upstream/mastercommand. For example:git checkout -b FORGE-123 upstream/master
-
Contribute new code or make changes to existing files. If you’re using Eclipse, be sure to format your code using the provided Forge Code Formatter). If you’re using IntelliJ IDEA, we recommend using this plugin to use the before-mentioned Eclipse code formatter in IDEA.
-
Use the
git addcommand to add new or changed file contents to the staging area. git add . -
Use the git status command to view the status of the files in the directory and in the staging area and ensure that all modified files are properly staged:
git status
-
Commit your changes to your local topic branch.
git commit -m 'FORGE-XX: Description of change...'
-
If you made multiple commits, or if there were any merge commits created when you pulled from upstream, use rebase to squash them into a single commit, where 5 is the number of commits to rebase:
git rebase -i HEAD~5
Change 'pick' to 'f' for each commit you wish to fixup upwards. (If you do not change a line, it will not be modified.)
1 pick ade2b1a FORGE-XX: Does something cool 2 f c3ae0a2 almost done 3 f c863bfb did more work 4 f af793ae Started working on FORGE-XX 5 pick 368bbb9 Previous commit written by someone else
Once you are done, your commits should look like this:
1 ade2b1a FORGE-XX: Does something cool 2 368bbb9 Previous commit written by someone else
You can view your commits by typing:
git log
-
Push your local topic branch to your github forked repository. This will create a branch on your Git fork repository with the same name as your local topic branch name.
git push origin HEAD
|
Important
|
The above command assumes your remote repository is named 'origin'. You can verify your forked remote repository name using the command git remote -v. |
-
Browse to the <topic-branch-name> branch on your forked Git repository and open a Pull Request. Give it a clear title and description.
Clone the repo (or your fork):
git clone git@github.com:forge/core.git
Use https://github.com/forge/core.git instead, if you do not have access, or clone the repo and use the fork’s URL.
Build:
mvn clean install
The Forge 2 distribution will be present in the dist/target directory. Unzip and extract to get started:
unzip dist/target/forge-distribution-<release_version>.zip -d ~ export FORGE_HOME=~/forge-distribution-<release_version> export PATH=$FORGE_HOME/bin:$PATH forge
JBoss Tools for Forge 2 will allow you to run Forge inside Eclipse. Build this only when you need to run Forge in Eclipse. The Forge-Core distribution is sufficient for the CLI mode.
Clone the repo (or your fork):
git clone git@github.com:jbosstools/jbosstools-forge.git
Include the required repositories in your settings.xml file, or copy the settings.xml from below and save it somewhere to use in the Maven build. This is also described in https://community.jboss.org/wiki/MavenGettingStarted-Developers:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>jboss-default</id>
<repositories>
<!-- To resolve parent artifact -->
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
</repository>
<repository>
<id>jboss-snapshots-repository</id>
<name>JBoss Snapshots Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url>
</repository>
</repositories>
<pluginRepositories>
<!-- To resolve parent artifact -->
<pluginRepository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
</pluginRepository>
<pluginRepository>
<id>jboss-snapshots-repository</id>
<name>JBoss Snapshots Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>jboss-default</activeProfile>
</activeProfiles>
</settings>mvn --settings ~/.m2/jbosstools.xml clean verify
The Forge 2.0 artifacts from your local .m2 repository would be included in the JBoss Tools plugins for Forge. You can install them in an Eclipse Kepler installation, by adding $JBOSSTOOLS_FORGE_DIR/site/target/forge.site-1.2.0-SNAPSHOT.zip as an update site.
Note, you may need to run git clean -fdx to clean the target directories of older snapshot artifacts.
To use the Maven artifacts from the JBoss Nexus repository instead of your local .m2 repository, run:
mvn -U --settings ~/.m2/jbosstools.xml clean verify
This section applies when you do not wish to build and install the Eclipse plugin in an installation, but just work on the Forge 2 sources and run it as an Eclipse application. This useful when you’re working on the Forge 2 sources instead of your own addons.
Import the following projects from the plugins/ module into your Eclipse workspace:
org.jboss.tools.aesh.core org.jboss.tools.aesh.runtime org.jboss.tools.aesh.ui org.jboss.tools.forge.core org.jboss.tools.forge.m2e org.jboss.tools.forge.runtime org.jboss.tools.forge.runtime.ext org.jboss.tools.forge.ui org.jboss.tools.forge.ui.notifications
Right-click the org.jboss.tools.forge.ui project, and choose Run As → Eclipse Application.
|
Important
|
If you are unable to run the project as an Eclipse application, the reason is that you don’t have the Tycho M2 Provider installed. If that’s the case, install it via this update site: http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-tycho/0.7.0/N/0.7.0.201309291400/ |
Right click the org.jboss.tools.forge.ui project, choose Run As → Run Configurations.. and set the VM arguments to: -Xmx1024m -XX:MaxPermSize=256m
If you’re wondering what issues would be suitable when you’re just getting started, we recommend taking a look at the issues with the 'starter' label in our JIRA.
-
JBoss Forge is licensed under the Eclipse Public License 1.0.
-
There is no need to sign a contributor agreement to contribute to JBoss Forge. You just need to explicitly license any contribution under the EPL 1.0. If you add any new files to JBoss Forge, make sure to add the correct header.
/** * Copyright 2015 Red Hat, Inc. and/or its affiliates. * * Licensed under the Eclipse Public License version 1.0, available at * http://www.eclipse.org/legal/epl-v10.html */
<!-- ~ Copyright 2015 Red Hat, Inc. and/or its affiliates. ~ ~ Licensed under the Eclipse Public License version 1.0, available at ~ http://www.eclipse.org/legal/epl-v10.html -->
# Copyright 2015 Red Hat, Inc. and/or its affiliates. # # Licensed under the Eclipse Public License version 1.0, available at # http://www.eclipse.org/legal/epl-v10.html
-- -- Copyright 2015 Red Hat, Inc. and/or its affiliates. -- -- Licensed under the Eclipse Public License version 1.0, available at -- http://www.eclipse.org/legal/epl-v10.html --