Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAGQtxvY4gdcS34DO9i7tJe-Tu4hg8zGuse-PVM0oFYvXsayK7w@mail.gmail.com>
References: 
 <CAGQtxvY4gdcS34DO9i7tJe-Tu4hg8zGuse-PVM0oFYvXsayK7w@mail.gmail.com>
From: David Nalley <david@gnsa.us>
Date: Tue, 15 Jul 2014 04:39:53 -0400
Message-ID: 
 <CAKprHVZiTkgQGuHrDJU1DJ_sXVTmE9gGkDPOkJjt7+M7cH=BKQ@mail.gmail.com>
Subject: Re: xapi jar as separate release
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: text/plain; charset=UTF-8

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 that we are currently using.

--David


On Mon, Jul 14, 2014 at 6:17 AM, Daan Hoogland <daan.hoogland@gmail.com> wrote:
> 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 to be to release the xapi module separately and
> create a release for it. I know that there has been some shifting back
> and forth with this module and I would like to get consensus to create
> a separate module and release for it.
>
> So my question: How do I get a version into the maven repo?
>
> thanks,
> --
> Daan