cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <>
Subject Re: CS4.0 build failed while setting up a dev environment on windows
Date Fri, 07 Dec 2012 02:21:02 GMT
Livio, you're using 4.0 release version. The commands you're using are for the master-git branch.
Follow instructions from here:

The build system in 4.0.0 was ant, so to deploy database, you would build it first, deploy
server and then do ant deploydb.

Hope this helps,

On 06-Dec-2012, at 6:12 PM, Livio Lv <> wrote:

> Rohit:
> Yes, I am in the top level directory, but downloading the source code from
> the site url of (Official
> Source Code Release apache-cloudstack-4.0.0-incubating-src.tar.bz2), not by
> git(there are some problem of httpproxy with my computer of WinXP32 OS). I
> have checked the "developer" directory , there are only one file named
> "pom.xml" in it.
> 2012/12/7 Rohit Yadav <>
>> Are you in the top level directory, within the git repo? The error
>> suggests it cannot find the developer project, check if you see a directory
>> with the name developer and it has a pom.xml etc. Also share your git
>> branch.
>> Regards.
>> On 05-Dec-2012, at 5:21 PM, Livio Lv <> wrote:
>>> Hi All:
>>> I have been setting up cloudstack4 dev environment on widows following
>>> the instruction of
>>> There are some problem while deploying the database with command of "mvn
>> -P
>>> developer -pl developer -Ddeploydb" on cygwin (Step 11 Build), Log as
>>> follows:
>>> $ mvn -P developer -pl developer -Ddeploydb
>>> [INFO] Scanning for projects...
>>> [ERROR] Could not find the selected project in the reactor: developer ->
>>> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e
>>> switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>>> Does anywhere have the same failure?

View raw message