Mvn.skip.tests=true will skip building the test jar. Running without that option should work.
Regards, Frank Apologies, sent that too early, last bit should be : Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000) Maven home: /usr/local/apache-maven-3.0.4 Java version: 1.7.0_75, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-504.12.2.el6.x86_64", arch: "amd64", family: "unix" Thanks! On Sat, Oct 10, 2015 at 4:00 PM, cs user <acldstk...@gmail.com> wrote: > Hi Folks, > > I'd really appreciate some help with this if anyone can spare a moment.... > :-) > > So I've checked out the repo and got to this stage in git: > > [csuser@localhost cloudstack]$ git status > # On branch origin/4.5 > nothing to commit (working directory clean) > > I've then done a mvn clean, and all is fine. > > I've then tried to compile with the following command: > > [csuser@localhost cloudstack]$ mvn -U -P impatient,developer > -Dmaven.test.skip=true -DskipTests > > However I keep getting the following: > > [INFO] Building Apache CloudStack Framework - Clustering 4.5.3-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > Downloading: > http://repository.apache.org/snapshots/org/apache/cloudstack/cloud-api/4.5.3-SNAPSHOT/maven-metadata.xml > Downloading: > http://repository.apache.org/snapshots/org/apache/cloudstack/cloud-api/4.5.3-SNAPSHOT/cloud-api-4.5.3-SNAPSHOT-tests.jar > SNIP > [ERROR] Failed to execute goal on project cloud-framework-cluster: Could > not resolve dependencies for project > org.apache.cloudstack:cloud-framework-cluster:jar:4.5.3-SNAPSHOT: Could not > find artifact org.apache.cloudstack:cloud-api:jar:tests:4.5.3-SNAPSHOT in > apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1] > > > This cloud-api-4.5.3-SNAPSHOT-tests.jar it mentions doesn't appear to > exist in the location it is trying to download it from. Just to note, I do > seem to be able to compile the master branch (4.6). That compiles and then > launches fine. > > Is there a way around this issue for the 4.5 branch? > > mvn -v shows: > > > >
