Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D72B5118E9 for ; Wed, 16 Jul 2014 04:42:45 +0000 (UTC) Received: (qmail 74509 invoked by uid 500); 16 Jul 2014 04:42:45 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 74470 invoked by uid 500); 16 Jul 2014 04:42:45 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 73903 invoked by uid 99); 16 Jul 2014 04:42:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jul 2014 04:42:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mike.tutkowski@solidfire.com designates 209.85.218.53 as permitted sender) Received: from [209.85.218.53] (HELO mail-oi0-f53.google.com) (209.85.218.53) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jul 2014 04:42:43 +0000 Received: by mail-oi0-f53.google.com with SMTP id e131so58100oig.12 for ; Tue, 15 Jul 2014 21:42:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=LdK6CXc4q3135qta/r8i6kCXz5+7BpJBigciyozeOQw=; b=HPJmsI6Wtr3yIQyVl9FlU+ZLUl+ecjJ7htnjsMJYwvtwK9Whh80m/1KyO6UI9ljuwe iBvGkVCSJ6Jpymik1BAq7lQLYTOfqE1Q9mXwxFdRMsfRyP81iwkkqjbr0divvQSZsP8F s2qrVRrlaN2Do+GY+3WwRfquWXfz3ir9svrx8KBTbglkWu3tLdK9qisAr6truzl65Whb N3pBxim/QGdgsl3JgqwspFxQmrwFVBcqbv1TXxAaCwcLYA3Ae6tnMT092ftPBTtfvDm3 LdsTaIUmQuRP7fk/qBkmrSRzUWAsqy9stBc0+BYD026ijuXCIM3BnSdM4NTSfyAXG1XZ PCKg== X-Gm-Message-State: ALoCoQkXJapf7csXxmrNOGGYXzgn7zf8RkMJ09neXb0GQOiyTupGeVCJfJDFc2igJ1H9p8uDeGp9 MIME-Version: 1.0 X-Received: by 10.182.97.97 with SMTP id dz1mr31653408obb.13.1405485737968; Tue, 15 Jul 2014 21:42:17 -0700 (PDT) Received: by 10.182.124.230 with HTTP; Tue, 15 Jul 2014 21:42:17 -0700 (PDT) In-Reply-To: <20CF38CB4385CE4D9D1558D52A0FC058774AF4@SJCPEX01CL03.citrite.net> References: <20CF38CB4385CE4D9D1558D52A0FC058774AF4@SJCPEX01CL03.citrite.net> Date: Tue, 15 Jul 2014 22:42:17 -0600 Message-ID: Subject: Re: xapi jar as separate release From: Mike Tutkowski To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=047d7b2e438626191e04fe4826a9 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e438626191e04fe4826a9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That's exactly what I was wondering, Alex. :) On Tue, Jul 15, 2014 at 3:13 PM, Alex Huang wrote: > I checked into master the changes that remove our copy and just use the > copy the XenServer team checked into maven. Is there any reason we're > talking about this? > > --Alex > > > -----Original Message----- > > From: David Nalley [mailto:david@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 not believe that we can sanely make= a > > separate release. Compared to bundling it with our release as we We hav= e > > 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 > > 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 bu= t > > > 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 bac= k > > > and forth with this module and I would like to get consensus to creat= e > > > a separate module and release for it. > > > > > > So my question: How do I get a version into the maven repo? > > > > > > thanks, > > > -- > > > Daan > --=20 *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkowski@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud *=E2=84=A2* --047d7b2e438626191e04fe4826a9--