> -----Original Message-----
> From: James Martin [mailto:jmar...@basho.com]
> Sent: Tuesday, October 02, 2012 9:23 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: updating cloudstack devcloud puppet recipes
> 
> Where's the best place to follow the new build instructions?
> 
> I was looking here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+Ma
> ven
> 
> built I need something that works with rdeploy.  Currently I've been
> doing:
> 
> mvn clean:clean
> mvn -P deps -pl deps
> mvn
> ant build-all rdeploy rdeploydb -Dport=7222

1. Hugo and I will work on using maven to deploydb and deploy server.
2. Right now, you can try http://evgeny-goldin.com/wiki/Sshexec-maven-plugin, 
or using vagrant to login into devcloud vm.

> 
> Thanks,
> 
> James
> 
> On Tue, Oct 2, 2012 at 10:02 AM, Chip Childers
> <chip.child...@sungard.com> wrote:
> > On Fri, Sep 21, 2012 at 5:29 AM, sebgoa <run...@gmail.com> wrote:
> 
> > James and Sebastien -
> >
> > I committed a couple of fixes to the build process, specifically to
> > install and use mvn.  I know that you guys are working on a cleaner
> > implementation (again, thanks), so I wanted you to be aware that the
> > source changed a little bit on that front.  I added a script to
> > download and install maven 3, and modified the code compile script to
> > use maven for the deps download step.
> >
> > -chip
> >
> >
> >> On Sep 20, 2012, at 11:33 PM, James Martin wrote:
> >>
> >>> Howdy folks.  Seems I sent this message to the old sourceforge list
> >>> earlier, if you have a duplicate, apologies (thanks to the kind
> soul
> >>> that pointed this out).
> >>>
> >>> I've been doing some work updating the devcloud puppet recipes --
> >>> cleaning them up, making them at little easier to read, etc.  I
> wanted
> >>> to make sure I was not duplicating anyone else's work before I
> >>> proceeded further.  I'll submit a patch within a week or so if all
> is
> >>> good.  Thanks!
> >>>
> >>>
> >>> -James
> >>
> >> -Sebastien Goasguen
> >>
> >>
> >>
> >>
> >>

Reply via email to