Kelven,
That makes sense. I'm not a committer so I'll probably be working off
my github account, but I'll base my branch off of javelin.
Darren
> Original Message
> Subject: Re: CS -> Spring
> From: Kelven Yang
> Date: Sat, August 18, 2012 7:31 pm
> To: "cloudstack-dev@inc
Darren,
I'll start some coding on architecture refactoring work at "javelin"
branch, and I'll use Spring too. Should we share the same branch? I've
pushed the branch to the ASF repo already
Kelven
On 8/18/12 6:59 PM, "Darren Shepherd" wrote:
>Alex,
>
>This is definitely post-4.0. I'm just th
Hi Jessica et al,
I migrated the S3 wiki page to the new wiki, the S3 doc is now at:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/S3+API+in+CloudStack
I put a redirect on the old page, I don't know if someone can actually lock the
edit.
Next, I will work on migrating the pdf info int
Alex,
This is definitely post-4.0. I'm just throwing the info out there of
what I'm thinking of doing just to see if there are any major
objections.
Regarding maven, I responded on the main thread for this just now, so
refer to that. Basically I've been waiting for a decision. I hadn't
been fo
All,
So I have maven fully functional. I sent an email regarding this but
being that it wasn't on this thread so it probably went un-noticed. So
below is basically a copy of that.
If you want to get an idea of what maven would look like for CS, what
I've done is on the "maven"
branch at https:/
Darren,
This is not going into 4.0 release right?
Also between maven and spring framework which one are you planning to do first?
The other thread regarding build system seems to be coming to a consensus when
the 4.0 release date is pushed back.
--Alex
> -Original Message-
> From:
I'm going to be starting the effort of moving CloudStack to be Spring
managed as this is an absolute must for me (and my day job). I wanted
to share some of the high level points and the scope as I see it today.
Moving to Spring should not impact much code (except swapping
annotations in a lot of
