compile the server?.
Requirements: Java, Maven and Files.
1) Download the GIT-client (you can find on Google.)
2) Create a directory, say tera
3) Right-click on the directory -> Git Bash
4) In console write:
Code:
git clone git: / / github.com / ATracer / tera-api.git
and press Enter, wait until the end of the operation.
5) Go into the directory \ tera \ tera-api \ com.tera (there is a project of aggregator), and run mvn clean install (or more to liking).
This is actually training. Successful compilation of the idea will not, therefore we will describe some of crutches and the overall work of a file:
1) Go to the directory \ tera \ tera-api \ com.tera and execute
Code:
copy pom.xml "% USERPROFILE% \. m2 \ repository \ com \ tera \ com.tera \ 1.0.0 \ com.tera-1.0.0.pom"
(We could and mvn install: install-file ..., but it is so sure). This is for WINDOWS and ways to check if that. If that is not so - and you can manually copy and rename. [This eliminates the error from the "lost" parent pom]
2) Dependence. I counted a few pieces that have not been found in dozens of repositories (of course due to specific versions and differences in group names, and artifacts). All changes will be in pom.xml, wrote about above (by the way, after the changes necessary to repeat the first step of copying, since the sub-charge dependence of the parent pom in the local repository).
a) org.eclipse: osgi: jar: 3.6.0.v20100517 [wrong artifact id]
add:
Code:
<dependency>
<groupId> org.eclipse.osgi </ groupId>
<artifactId> org.eclipse. osgi </ artifactId>
<version> $ {equinox.version} </ version>
</ Dependency>
b) com.google.inject: guice: jar: snapshot-r1189, com.google.inject: guice-assistedinject: jar: snapshot-r1189
change the version from the snapshot-r1189 for 2.0
Code:
<guice.version> 2.0 </ guice.version>
Edit the group id and artifact:
Code:
<dependency>
<groupId> com.google.inject. extensions </ groupId>
<artifactId> guice-assisted - inject </ artifactId>
<version> $ {guice.version} </ version>
<type> jar </ type>
</ Dependency>
a) trove: trove: jar: 2.1.0
take a bit older than the alternative (to replace the relationship):
Code:
<dependency>
<groupId> net.sf.trove4j </ groupId>
<artifactId> trove4j </ artifactId>
<version> 2.0.2 </ version>
</ Dependency>
Next, go to com.tera.common.database:
here as an option can be used instead of the usual artifacts bundle (selection - drank) -
Code:
<Embed-Dependency> Mysql-connector-java-bundle, sqlite-jdbc-bundle, commons-dbcp </ Embed-Dependency>
Code:
<dependency>
<groupId> mysql </ groupId>
<artifactId> mysql-connector-java-bundle </ artifactId>
<version> 5.1.13 </ version>
</ Dependency>
<dependency>
<groupId> org.xerial </ groupId>
<artifactId> sqlite-jdbc-bundle </ artifactId>
<version> 3.7.2 </ version>
</ Dependency>
Also, all sub-com.tera.common .* there is a dependence in the netty-3.2.1.Final (second herd of dependency managment .) As the worst, but the fastest solution - add to all the pom.xml repository with this artifact:
Code:
<repositories>
<repository>
<id> atlassian-groups-public-m2-repo </ id>
<name> Atlassian Groups Public Maven 2 Repository </ name>
<url> https://maven.atlassian.com/content/groups/public </ url>
<snapshots>
<enabled> true </ enabled>
</ Snapshots>
<releases>
<enabled> true </ enabled>
</ Releases>
</ Repository>
</ Repositories>
By the way, some tests fail, so we can process them off (not good) --Dmaven.test.skip = true
Finally it should be noted that out rather than manual, and the hint "where to dig." On the example I showed com.tera.common .* What can be expected mainly in compiling the default profile and the others who also need to compile. Example:
Code:
mvn clean install-P id_profilya
Actually id: gapi, gsaion, lapi, lsaion and paion.
ZY If nothing is clear - it is better to learn or be postponed until better times. Now version of the project 0.0.6-SNAPSHOT, which means it is still unstable, and much will change, maybe ...
no points of playing unless they have English patches for it.
