Craig Lawson created CLOUDSTACK-10291:

             Summary: unable to package 4.11 for cents 7
                 Key: CLOUDSTACK-10291
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Install and Setup
    Affects Versions:
         Environment: centos7
            Reporter: Craig Lawson

Apologies if I've missed something or this is not the right place, I'm keen to 
get rocking with cloudstack and this is preventing me from getting this into 

As your site advertises the current LTS release being 4.11 I've been trying to 
get this running, I notice there are no community released RPM's and want to 
mange the installations via yum.

I've followed the docs shipped with the source to create the packages and get 
stuck at the same point - either by using the released sources, or by checking 
out the git repository on the 4.11 branch (version

After building, I pop to the package directory and set things off but end up 
with the following packaging error -
[root@XNET packaging]# ./ --p noredist -d centos7
 --pack:simulator:distribution:release noredist -d centos7 --
Preparing to package Apache CloudStack
. preparing source tarball
. executing rpmbuild
error: Failed build dependencies:
 maven >= 3.0.0 is needed by cloudstack-
RPM Build Failed{noformat}
However - maven version is 3.5 -
[root@XNET packaging]# mvn -v
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 
Maven home: /usr/local/maven
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64", family: 
Completely stuck here and unable to build the packages - have I missed 
something, is it possible to use this version yet? As LTS is ending in a few 
months on 4.9 and 4.10 is not listed with LTS support we're keen to get this 
version running.


This message was sent by Atlassian JIRA

Reply via email to