|
TestingSnapshotBuilds
How to get access to Snapshot build and test work in progress
Featured Testing Snapshot BuildsStarting with the 1.5.0 release I will publish build with some meaningful changes to a small Maven repository on the main site. This procedure summarizes what you need to run VCC from these Snapshot builds. 1) Download and install version 2.2.1 or 2.0.11 (for instructions see Maven Site) 2) Create a directory to house a configuration file and fs-wc directory from your current VCC install, lets say: vcc-snapshot 3) Copy or link the content of fs-wc to vcc-snapshot 4) Create a file called pom.xml and add the content at the end of this file to it. 5) Go to vcc-snapshot and run the following command: <path-to-maven>/mvn exec:java -Dexec.mainClass=vcc.Main In my case (on a Mac) my maven was on the home directory so: ~/apache-maven-2.0.11/bin/mvn exec:java -Dexec.mainClass=vcc.Main Maven will download a ton of files (this is normal), including all the VCC files from the http://www.exnebula.org/ site. After the first time it will not download as many this. To force maven to check for newer SNAPSHOT use: ~/apache-maven-2.0.11/bin/mvn exec:java -Dexec.mainClass=vcc.Main If you monster don't appear nicely formatted you forgot to link/copy the fs-wc directory. Notes for Windows UserIn order to run Maven on Windows, you have to set the JAVA_HOME. You can do this at the Windows level (See this procedure). Another alternative is to edit the MVN.BAT in the Maven directory. Set Line 40 (or the one that has JAVA_HOME) to: set JAVA_HOME="C:\Progra~1\Java\jdk1.6.0_22" If you don't have the JDK using this may work: set JAVA_HOME="C:\Progra~1\Java\jre6" Do not use spaces in the variable, the example below will not work: set JAVA_HOME="C:\Program Files\Java\jre6" Notes for Mac Usersa) VCC requires Java 1.6 which is not always the default version, if VCC fails to start with popup message, execute this then run maven again: export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/ This will make the current terminal point to the correct version of java. b) If you downloaded the Application Bundle (vcc-1.4.0.dmg) and installed it (let's say in Applications), you have to do this command once to get the correct content from fs-wc: cd vcc-snapshot ln -s /Applications/Virtual\ Combat\ Cards.app/Contents/Resources/Java/fs-wc This will create a symbolic link to the fs-wc in the application bundle. Nightly POMThe following POM should be used for the 1.6.0-SNAPSHOT <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.exnebula</groupId>
<artifactId>vcc-nightly</artifactId>
<version>1.0.0-SNAPSHOT</version>
<description>Night VCC Execute</description>
<organization>
<name>exnebula.org</name>
<url>http://www.exnebula.org/</url>
</organization>
<name>Virtual Combat Cards 4E</name>
<inceptionYear>2008</inceptionYear>
<properties>
<scala.version>2.8.1</scala.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<repositories>
<repository>
<id>exnebula.org</id>
<name>ExNebelua Repository</name>
<url>http://www.exnebula.org/files/repo</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>org.exnebula</groupId>
<artifactId>vcc-main</artifactId>
<version>1.7.0-SNAPSHOT</version>
</dependency>
</dependencies>
</project>
|