src/main | ||
.gitattributes | ||
.gitignore | ||
build.gradle | ||
build.properties | ||
COPYING | ||
COPYING.LESSER | ||
README.md | ||
version.xml |
##Welcome to Equivalent Exchange 3! LATEST OFFICIAL VERSION: EE3 pre1h for 1.5.1/1.5.2
Compiling EE3 - For those that want the latest unreleased features.
Contributing - For those that want to help out.
FAQ - For those that have questions.
###Compiling Equivalent Exchange 3 IMPORTANT: Please report any issues you have, there might be some problems with the documentation! Also make sure you know EXACTLY what you're doing! It's not any of our faults if your OS crashes, becomes corrupted, etc.
####Setup Java The Java JDK is used to compile EE3.
- Download and install the Java JDK.
- Windows/Mac download link. Scroll down, accept the
Oracle Binary Code License Agreement for Java SE
, and download it (if you have a 64-bit OS, please download the 64-bit version). - Linux: Installation methods for certain popular flavors of Linux are listed below. If your distribution is not listed, follow the instructions specific to your package manager or install it manually here.
- Gentoo:
emerge dev-java/oracle-jdk-bin
- Archlinux:
pacman -S jdk7-openjdk
- Ubuntu/Debian:
apt-get install openjdk-7-jdk
- Fedora:
yum install java-1.7.0-openjdk
- Gentoo:
- Windows/Mac download link. Scroll down, accept the
- Windows: Set environment variables for the JDK.
- Go to
Control Panel\System and Security\System
, and click onAdvanced System Settings
on the left-hand side. - Click on
Environment Variables
. - Under
System Variables
, clickNew
. - For
Variable Name
, inputJAVA_HOME
. - For
Variable Value
, input something similar toC:\Program Files\Java\jdk1.7.0_45
exactly as shown (or wherever your Java JDK installation is), and clickOk
. - Scroll down to a variable named
Path
, and double-click on it. - Append
;%JAVA_HOME%\bin
EXACTLY AS SHOWN and clickOk
. Make sure the location is correct; double-check just to make sure.
- Go to
- Open up your command line and run
javac
. If it spews out a bunch of possible options and the usage, then you're good to go. If not, either try the steps again or check the FAQ.
####Setup Gradle Gradle is used to execute the various build tasks when compiling EE3.
- Download and install Gradle.
- Windows/Mac download link. You only need the binaries, but choose whatever flavor you want.
- Unzip the package and put it wherever you want, eg
C:\Gradle
.
- Unzip the package and put it wherever you want, eg
- Linux: Installation methods for certain popular flavors of Linux are listed below. If your distribution is not listed, follow the instructions specific to your package manager or install it manually here.
- Gentoo:
emerge dev-java/gradle-bin
- Archlinux: You'll have to install it from the AUR
- Ubuntu/Debian:
apt-get install gradle
- Fedora:
yum install gradle
- Gentoo:
- Windows/Mac download link. You only need the binaries, but choose whatever flavor you want.
- Windows: Set environment variables for Gradle.
- Go back to
Environment Variables
and then create a new system variable. - For
Variable Name
, inputGRADLE_HOME
. - For
Variable Value
, input something similar toC:\Gradle-1.10
exactly as shown (or wherever your Gradle installation is), and clickOk
. - Scroll down to
Path
again, and append;%GRADLE_HOME%\bin
EXACTLY AS SHOWN and clickOk
. Once again, double-check the location.
- Go back to
- Open up your command line and run
gradle
. If it says "Welcome to Gradle [version].", then you're good to go. If not, either try the steps again or check the FAQ.
####Setup Git Git is used to clone EE3 and update your local copy.
- Download and install Git here.
- Optional: Download and install a Git GUI client, such as Github for Windows/Mac, SmartGitHg, TortoiseGit, etc. A nice list is available here.
####Setup EE3 This section assumes that you're using the command-line version of Git.
- Open up your command line.
- Navigate to a place where you want to download EE3's source (eg
C:\Github\Equivalent-Exchange-3\
) by executingcd [folder location]
. This location is known asmcdev
from now on. - Execute
git clone https://github.com/pahimar/Equivalent-Exchange-3.git
. This will download EE3's source intomcdev
. - Right now, you should have a directory that looks something like:
mcdev
\-Equivalent-Exchange-3
\-EE3's files (should have `build.gradle`)
####Compile EE3
- Execute
gradle setupDevWorkspace
. This sets up Forge and downloads the necessary libraries to build EE3. This might take some time, be patient.- You will generally only have to do this once until the Forge version in
build.properties
changes.
- You will generally only have to do this once until the Forge version in
- Execute
gradle build
. If you did everything right,BUILD SUCCESSFUL
will be displayed after it finishes. This should be relatively quick.- If you see
BUILD FAILED
, check the error output (it should be right aroundBUILD FAILED
), fix everything (if possible), and try again.
- If you see
- Go to
mcdev\Equivalent-Exchange-3\build\libs
.- You should see a
.jar
file namedEquivalentExchange3-0.0.#.jar
, where # is thebuild_number
value inbuild.properties
.
- You should see a
- Copy the jar into your Minecraft mods folder, and you are done!
####Updating Your Repository In order to get the most up-to-date builds, you'll have to periodically update your local repository.
- Open up your command line.
- Navigate to
mcdev
in the console. - Make sure you have not made any changes to the local repository, or else there might be issues with Git.
- If you have, try reverting them to the status that they were when you last updated your repository.
- Execute
git pull master
. This pulls all commits from the official repository that do not yet exist on your local repository and updates it.
###Contributing
####Submitting a PR So you found a bug in pahimar's code? Think you can make it more efficient? Want to help in general? Great!
- If you haven't already, create a Github account.
- Click the
Fork
icon located at the top-right of this page (below your username). - Make the changes that you want to and commit them.
- If you're making changes locally, you'll have to do
git commit -a
andgit push
in your command line.
- If you're making changes locally, you'll have to do
- Click
Pull Request
at the right-hand side of the gray bar directly below your fork's name. - Click
Click to create a pull request for this comparison
, enter your PR's title, and create a detailed description telling pahimar what you changed. - Click
Send pull request
, and wait for feedback!
####Creating an Issue EE3 crashes every time? Have a suggestion? Found a bug? Create an issue now!
- Make sure your issue hasn't already been answered or fixed. Also think about whether your issue is a valid one before submitting it.
- Go to the issues page.
- Click
New Issue
right belowStar
andFork
. - Enter your Issue's title (something that summarizes your issue), and then create a detailed description ("Hey pahimar, could you add/change xxx?" or "Hey, found an exploit: stuff").
- If you are reporting a bug report from an unofficial version, make sure you include the following:
- Commit SHA (usually located in a changelog or the jar name itself)
- ForgeModLoader log
- Server log (if applicable)
- Detailed description of the bug
- If you are reporting a bug report from an unofficial version, make sure you include the following:
- Click
Submit new issue
, and wait for feedback!
###FAQ Answers to frequently reported issues and/or questions.
Q: What's a command line?
A: The command line is at the heart of every operating system. It's Command Prompt
for Windows and Terminal
for Mac and Linux.
Q: javac
or gradle
keeps giving me an error!
A: Make sure the locations you typed are correct. For example, if you typed C:\Java
for JAVA_HOME
, make sure C:\Java
exists, and there's a bin
folder inside of it.
Q: Gradle keeps saying BUILD FAILED
and I don't know how to fix it!
A: Make sure you executed gradle setupDevWorkspace
. If you already did, try doing it again. If it still fails, try creating an issue.
Q: My issue/PR was closed! A: Somebody probably commented and solved your issue, or it was opened a long time ago. If it's a PR, check to see if there's a commit message right before it was closed. If so, pahimar either pulled your PR or found a different way to do it.