Mailing-List: contact kerby-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kerby@directory.apache.org
MIME-Version: 1.0
In-Reply-To: <5597793B.7080208@gmail.com>
References: 
 <8D5F7E3237B3ED47B84CF187BB17B66611B8E673@SHSMSX103.ccr.corp.intel.com>
	<CABzFU-cB9E0=2NyV5vprR0TPpUxwk+BW111BdZ+JXEXWUZT-bw@mail.gmail.com>
	<8D5F7E3237B3ED47B84CF187BB17B66611B8E713@SHSMSX103.ccr.corp.intel.com>
	<CABzFU-fRyjJCW4RK34L+_Dq44+vAwrHCWe-C--49N1QHpeO=Hg@mail.gmail.com>
	<559774A1.5020707@gmail.com>
	<CABzFU-exXE8vRHgmk_GjOeXytaXxJs_vbVryQS-7DXOg_eFBfg@mail.gmail.com>
	<5597793B.7080208@gmail.com>
Date: Sat, 4 Jul 2015 14:44:09 +0800
Message-ID: 
 <CABzFU-cp4mO=HZ6PBT3BOkpuscz2vvP88-vBcjteLL89LBRzcA@mail.gmail.com>
Subject: Re: Kerby building fails
From: Kiran Ayyagari <kayyagari@apache.org>
To: kerby@directory.apache.org
Content-Type: multipart/alternative; boundary=20cf30434842eb0094051a06ff8b

--20cf30434842eb0094051a06ff8b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 4, 2015 at 2:12 PM, Emmanuel L=C3=A9charny <elecharny@gmail.com=
>
wrote:

> Le 04/07/15 07:55, Kiran Ayyagari a =C3=A9crit :
> > On Sat, Jul 4, 2015 at 1:52 PM, Emmanuel L=C3=A9charny <elecharny@gmail=
.com>
> > wrote:
> >
> >> Le 04/07/15 07:49, Kiran Ayyagari a =C3=A9crit :
> >>> On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <kai.zheng@intel.com>
> wrote:
> >>>
> >>>> Thanks Kiran.
> >>>>
> >>>>>> you need latest mavibot build in your local repo
> >>>> Do we have to rely on this? Maybe we could use some public version? =
If
> >> not
> >>>> then when could we have the new release version?
> >>>> I do have the local build of Mavibot, but am not sure all Kerby
> >> developers
> >>>> do.
> >>>>
> >>> It is available in the repository
> >>> https://repository.apache.org/content/groups/snapshots
> >>>
> >>> Those who do not want to build it locally can use this configuration
> >>> http://apaste.info/qLE to set their
> >>> maven setting.xml (either create new file or update existing
> accordingly)
> >> That's not a good idea, IMO.
> >>
> >> both are in development, so I don't see any issue with it
> >> We should never depend on a SNAPSHOT. I'd rather cut a release of
> >> MAVIBOT and make Kerby depend on this release, but in the mean time, I
> >> strongly suggest the module not to be added (or to be commented) in th=
e
> >> kerby build.
> >>
> > if a release version of Kerby depends on a snapshot then agree, but tha=
t
> is
> > not the case here
> >
> >
> >
> No, even if it's not a release : depending on a SNAPSHOT is risky. It's
> not like ApacheDS which depends on the API and Mavibot SNAPSHOT, because
> we can't imagine releasing apacheDS without releasing Mavibot and the
> API first. That creates a dependency on an external project that is
> problematic.
>
> Here, what I would suggest is to add a maven profile, so that you can
> build Kerby with a Mavibot SNAPSHOT, like : mvn -Pmavibot
>
> Now, I see where you are coming from, and from a develoment POV, your
> choice make sense. It's just that for others, it breaks the build.
>
> Here is what we should do : cut a MAVIBOT release, now. That would solve
> the issue.
>
> +1

> wdyt ?
>

we are going to release Mavibot soon anyway, I was just pointing that it is
not a blocker for
building kerby with mavibot module, and maven is there to solve cases like
this.

I wouldn't have depended on a snapshot if it is a library outside Directory
project.


--=20
Kiran Ayyagari
http://keydap.com

--20cf30434842eb0094051a06ff8b--