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: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 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.hoogl...@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
