s been in master for 3 months now and people seem to be fine with it.
> You'll be the judge if you like to pull it in.
>
> --Alex
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Wednesday, July 16, 2014 7:48 AM
&g
ou like to pull it in.
--Alex
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, July 16, 2014 7:48 AM
> To: dev
> Subject: Re: xapi jar as separate release
>
> The question put in line with actuality: is the rc I just baked
t it? Which is BSD
> licensed.
>
> --
> Stephen Turner
>
>
> -Original Message-
> From: Tim Mackey [mailto:tmac...@gmail.com]
> Sent: 16 July 2014 14:39
> To: dev@cloudstack.apache.org
> Subject: Re: xapi jar as separate release
>
> Curious
This is just the xapi SDK we're talking about, isn't it? Which is BSD licensed.
--
Stephen Turner
-Original Message-
From: Tim Mackey [mailto:tmac...@gmail.com]
Sent: 16 July 2014 14:39
To: dev@cloudstack.apache.org
Subject: Re: xapi jar as separate release
Curious if
he
> > >> copy the XenServer team checked into maven. Is there any reason we're
> > >> talking about this?
> > >>
> > >> --Alex
> > >>
> > >> > -Original Message-
> > >> > From: David Nalley [mailto:da...@gnsa.us
XenServer team checked into maven. Is there any reason we're
> >> talking about this?
> >>
> >> --Alex
> >>
> >> > -Original Message-
> >> > From: David Nalley [mailto:da...@gnsa.us ]
> >> > Sent: Tuesday, July 15, 20
s]
>> > Sent: Tuesday, July 15, 2014 1:40 AM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: xapi jar as separate release
>> >
>> > XAPI is not an apache project. I do not believe that we can sanely make a
>> > separate release. Compare
ut this?
>
> --Alex
>
> > -Original Message-
> > From: David Nalley [mailto:da...@gnsa.us]
> > Sent: Tuesday, July 15, 2014 1:40 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: xapi jar as separate release
> >
> > XAPI is not an apache project. I do n
0 AM
> To: dev@cloudstack.apache.org
> Subject: Re: xapi jar as separate release
>
> XAPI is not an apache project. I do not believe that we can sanely make a
> separate release. Compared to bundling it with our release as we We have
> essentially 'forked' XAPI from the
XAPI is not an apache project. I do not believe that we can sanely
make a separate release. Compared to bundling it with our release as
we We have essentially 'forked' XAPI from the upstream at Xen Project
and made our own changes. Those changes are in the latest version
AIUI, but not the version t
Please note the alternatives:
1 Setting the dependency to the release version.
2 Undoing the setting of the module version to the release version
I can do these two rather quickly but would rather take the correct approach.
commends, please??
Daan
On Mon, Jul 14, 2014 at 12:17 PM, Daan Hoogland
LS,
One of the issues with the last RC was that the cloudstack xapi was
not a released version (i.e. 6.2.0-1-SNAPSHOT). In the release build
it was numbered as 6.2.0-1 but not referred by that release number but
by the snapshot id. There are several solutions to this. The most
correct would seem t
12 matches
Mail list logo
