Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAKprHVYReGwK8TxzuC4z=SiUAOqbYA=QvYFRNO1UMecOwbfY_Q@mail.gmail.com>
References: <6DE00C9FDF08A34683DF71786C70EBF0294ACA6B@SBPOMB402.sbp.lan>
 <CAKprHVYReGwK8TxzuC4z=SiUAOqbYA=QvYFRNO1UMecOwbfY_Q@mail.gmail.com>
From: David Nalley <david@gnsa.us>
Date: Wed, 6 Jun 2012 23:58:14 -0400
Message-ID: 
 <CAKprHVYz4i++32YZVL0Gne8UFPJACF5-VeUu+fRptT_Wm2qA4Q@mail.gmail.com>
Subject: Re: Which branch to Nicira integration?
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 6, 2012 at 10:52 PM, David Nalley <david@gnsa.us> wrote:
> On Wed, Jun 6, 2012 at 9:19 PM, Hugo Trippaers
> <HTrippaers@schubergphilis.com> wrote:
>> Heya all,
>>
>> This afternoon we had a nice chat with Chiradeep about the Nicira integr=
ation. It's moving along nicely know.
>>
>> However while setting up a test environment with a branch containing new=
 code, i ran into trouble with the secondary storage vm. Troubleshooting th=
at i found that the master brach (which i used to base my changes on) is la=
cking all build steps for the console-proxy.
>>
>> So my questions are
>> which branch should i base my changes and eventual patch on? 3.0.x, mast=
er or another one?
>> If master, why is the console-proxy taken out and how to work around thi=
s?
>>
>
>
> You should definitely be building off of a branch based on master in
> the git repo - what errors are you seeing with the console proxy? =A0We
> likely need to fix that.
>
> --David

That's my fault. I ripped console proxy out of the build-cloud.xml
when I was removing it from the RPM (no idea what possessed me to do
that), and if you didn't need to build systemVMs you wouldn't have
noticed it missing. I just pushed that back in - but it's no longer
part of build-all - but you should be able to build it (and the rest
of CloudStack) with:

ant build-console-proxy build-all

Let me know if you run into problems.

--David