You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kerby@directory.apache.org by "Zheng, Kai" <ka...@intel.com> on 2015/07/04 05:51:22 UTC
Kerby building fails
Hi Kiran,
It always fails on my side as below. Isn't the artifact already pushed to the public, or should we use any public available one? Thanks.
Regards,
Kai
[INFO] Kerby Kdc Test .................................... SUCCESS [33.404s]
[INFO] Mavibot based backend ............................. FAILURE [0.022s]
[INFO] Kerby Distribution ................................ SKIPPED
[INFO] KDC Dist .......................................... SKIPPED
[INFO] Tool Dist ......................................... SKIPPED
[INFO] Kerby benchmark ................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:00.671s
[INFO] Finished at: Sat Jul 04 11:48:00 CST 2015
[INFO] Final Memory: 54M/335M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project mavibot-backend: Could not resolve dependencies for project org.apache.kerby:mavibot-backend:jar:1.0-SNAPSHOT: Could not find artifact org
.apache.directory.mavibot:mavibot:jar:1.0.0-M8-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :mavibot-backend
RE: Kerby building fails
Posted by "Zheng, Kai" <ka...@intel.com>.
I guess it's still in WIP, so I shouldn't have added the WIP module to the parent module, so my latest commit has reverted the change back, removing the WIP module out of the parent for now.
-----Original Message-----
From: Zheng, Kai [mailto:kai.zheng@intel.com]
Sent: Saturday, July 04, 2015 11:51 AM
To: kerby@directory.apache.org
Subject: Kerby building fails
Hi Kiran,
It always fails on my side as below. Isn't the artifact already pushed to the public, or should we use any public available one? Thanks.
Regards,
Kai
[INFO] Kerby Kdc Test .................................... SUCCESS [33.404s] [INFO] Mavibot based backend ............................. FAILURE [0.022s] [INFO] Kerby Distribution ................................ SKIPPED [INFO] KDC Dist .......................................... SKIPPED [INFO] Tool Dist ......................................... SKIPPED [INFO] Kerby benchmark ................................... SKIPPED [INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:00.671s
[INFO] Finished at: Sat Jul 04 11:48:00 CST 2015 [INFO] Final Memory: 54M/335M [INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project mavibot-backend: Could not resolve dependencies for project org.apache.kerby:mavibot-backend:jar:1.0-SNAPSHOT: Could not find artifact org .apache.directory.mavibot:mavibot:jar:1.0.0-M8-SNAPSHOT -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :mavibot-backend
RE: Kerby building fails
Posted by "Zheng, Kai" <ka...@intel.com>.
Yes, the workaround is OK to me too.
Regards,
Kai
-----Original Message-----
From: Emmanuel Lécharny [mailto:elecharny@gmail.com]
Sent: Saturday, July 04, 2015 9:02 PM
To: kerby@directory.apache.org
Subject: Re: Kerby building fails
Le 04/07/15 14:50, Zheng, Kai a écrit :
> Thanks Emmanuel and Kiran for the discussion and getting the building passed by default anyway.
> Hope we could have a formal Mavibot release not too late before Kerby's first release, so it won't depend on the snapshot.
We *could* depend on a SNAPSHOT, but that would require a discussion about it.ATM, the workaround is ok.
/me will be MIA for a couple of days...
Re: Kerby building fails
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 04/07/15 14:50, Zheng, Kai a écrit :
> Thanks Emmanuel and Kiran for the discussion and getting the building passed by default anyway.
> Hope we could have a formal Mavibot release not too late before Kerby's first release, so it won't depend on the snapshot.
We *could* depend on a SNAPSHOT, but that would require a discussion
about it.ATM, the workaround is ok.
/me will be MIA for a couple of days...
RE: Kerby building fails
Posted by "Zheng, Kai" <ka...@intel.com>.
Thanks Emmanuel and Kiran for the discussion and getting the building passed by default anyway.
Hope we could have a formal Mavibot release not too late before Kerby's first release, so it won't depend on the snapshot.
Regards,
Kai
-----Original Message-----
From: Kiran Ayyagari [mailto:kayyagari@apache.org]
Sent: Saturday, July 04, 2015 7:58 PM
To: kerby@directory.apache.org
Subject: Re: Kerby building fails
On Sat, Jul 4, 2015 at 3:22 PM, Emmanuel Lécharny <el...@gmail.com>
wrote:
> Le 04/07/15 08:44, Kiran Ayyagari a écrit :
> > On Sat, Jul 4, 2015 at 2:12 PM, Emmanuel Lécharny
> > <el...@gmail.com>
> > wrote:
> >
> >> Le 04/07/15 07:55, Kiran Ayyagari a écrit :
> >>> On Sat, Jul 4, 2015 at 1:52 PM, Emmanuel Lécharny
> >>> <elecharny@gmail.com
> >
> >>> wrote:
> >>>
> >>>> Le 04/07/15 07:49, Kiran Ayyagari a écrit :
> >>>>> On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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
> the
> >>>> kerby build.
> >>>>
> >>> if a release version of Kerby depends on a snapshot then agree,
> >>> but
> that
> >> 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.
> This is not the right way to use Maven : you are just telling anyone
> that will download Kerby source that they are to tune their
> settings.xml. It's not flying !
>
I was just letting those new kerby developers who I think are new to maven.
>
> Also consider that the buldbot is failing, generating errors that we
> all receive, and we have no way to change the buildbot settings.xml.
>
> I will look into it, wonder why snapshot repo is not added by default
> in
the buildbot
I might just add repository tag in pom.xml to fix this for everybody
> Add a Maven profile if you are to use a Mavibot SNAPSHOT.
>
>
sorry, if I thought this is the right way to do I would have done it, but it is counter intuitive developers are supposed to figure out their tools and environment issues.
--
Kiran Ayyagari
http://keydap.com
Re: Kerby building fails
Posted by Kiran Ayyagari <ka...@apache.org>.
On Sat, Jul 4, 2015 at 3:22 PM, Emmanuel Lécharny <el...@gmail.com>
wrote:
> Le 04/07/15 08:44, Kiran Ayyagari a écrit :
> > On Sat, Jul 4, 2015 at 2:12 PM, Emmanuel Lécharny <el...@gmail.com>
> > wrote:
> >
> >> Le 04/07/15 07:55, Kiran Ayyagari a écrit :
> >>> On Sat, Jul 4, 2015 at 1:52 PM, Emmanuel Lécharny <elecharny@gmail.com
> >
> >>> wrote:
> >>>
> >>>> Le 04/07/15 07:49, Kiran Ayyagari a écrit :
> >>>>> On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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
> the
> >>>> kerby build.
> >>>>
> >>> if a release version of Kerby depends on a snapshot then agree, but
> that
> >> 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.
> This is not the right way to use Maven : you are just telling anyone
> that will download Kerby source that they are to tune their
> settings.xml. It's not flying !
>
I was just letting those new kerby developers who I think are new to maven.
>
> Also consider that the buldbot is failing, generating errors that we all
> receive, and we have no way to change the buildbot settings.xml.
>
> I will look into it, wonder why snapshot repo is not added by default in
the buildbot
I might just add repository tag in pom.xml to fix this for everybody
> Add a Maven profile if you are to use a Mavibot SNAPSHOT.
>
>
sorry, if I thought this is the right way to do I would have done it, but
it is counter intuitive
developers are supposed to figure out their tools and environment issues.
--
Kiran Ayyagari
http://keydap.com
Re: Kerby building fails
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 04/07/15 08:44, Kiran Ayyagari a écrit :
> On Sat, Jul 4, 2015 at 2:12 PM, Emmanuel Lécharny <el...@gmail.com>
> wrote:
>
>> Le 04/07/15 07:55, Kiran Ayyagari a écrit :
>>> On Sat, Jul 4, 2015 at 1:52 PM, Emmanuel Lécharny <el...@gmail.com>
>>> wrote:
>>>
>>>> Le 04/07/15 07:49, Kiran Ayyagari a écrit :
>>>>> On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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 the
>>>> kerby build.
>>>>
>>> if a release version of Kerby depends on a snapshot then agree, but that
>> 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.
This is not the right way to use Maven : you are just telling anyone
that will download Kerby source that they are to tune their
settings.xml. It's not flying !
Also consider that the buldbot is failing, generating errors that we all
receive, and we have no way to change the buildbot settings.xml.
Add a Maven profile if you are to use a Mavibot SNAPSHOT.
Re: Kerby building fails
Posted by Kiran Ayyagari <ka...@apache.org>.
On Sat, Jul 4, 2015 at 2:12 PM, Emmanuel Lécharny <el...@gmail.com>
wrote:
> Le 04/07/15 07:55, Kiran Ayyagari a écrit :
> > On Sat, Jul 4, 2015 at 1:52 PM, Emmanuel Lécharny <el...@gmail.com>
> > wrote:
> >
> >> Le 04/07/15 07:49, Kiran Ayyagari a écrit :
> >>> On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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 the
> >> kerby build.
> >>
> > if a release version of Kerby depends on a snapshot then agree, but that
> 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.
--
Kiran Ayyagari
http://keydap.com
Re: Kerby building fails
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 04/07/15 07:55, Kiran Ayyagari a écrit :
> On Sat, Jul 4, 2015 at 1:52 PM, Emmanuel Lécharny <el...@gmail.com>
> wrote:
>
>> Le 04/07/15 07:49, Kiran Ayyagari a écrit :
>>> On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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 the
>> kerby build.
>>
> if a release version of Kerby depends on a snapshot then agree, but that 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.
wdyt ?
Re: Kerby building fails
Posted by Kiran Ayyagari <ka...@apache.org>.
On Sat, Jul 4, 2015 at 1:52 PM, Emmanuel Lécharny <el...@gmail.com>
wrote:
> Le 04/07/15 07:49, Kiran Ayyagari a écrit :
> > On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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 the
> kerby build.
>
if a release version of Kerby depends on a snapshot then agree, but that is
not the case here
--
Kiran Ayyagari
http://keydap.com
Re: Kerby building fails
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 04/07/15 07:49, Kiran Ayyagari a écrit :
> On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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.
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 the
kerby build.
Re: Kerby building fails
Posted by Kiran Ayyagari <ka...@apache.org>.
On Sat, Jul 4, 2015 at 1:20 PM, Zheng, Kai <ka...@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)
> Regards,
> Kai
>
> -----Original Message-----
> From: Kiran Ayyagari [mailto:kayyagari@apache.org]
> Sent: Saturday, July 04, 2015 1:15 PM
> To: kerby@directory.apache.org
> Subject: Re: Kerby building fails
>
> On Sat, Jul 4, 2015 at 11:51 AM, Zheng, Kai <ka...@intel.com> wrote:
>
> > Hi Kiran,
> >
> > It always fails on my side as below. Isn't the artifact already pushed
> > to the public, or should we use any public available one? Thanks.
> >
> > Regards,
> > Kai
> >
> > [INFO] Kerby Kdc Test .................................... SUCCESS
> > [33.404s] [INFO] Mavibot based backend .............................
> > FAILURE [0.022s] [INFO] Kerby Distribution
> > ................................ SKIPPED [INFO] KDC Dist
> > .......................................... SKIPPED [INFO] Tool Dist
> > ......................................... SKIPPED [INFO] Kerby
> > benchmark ................................... SKIPPED [INFO]
> > ----------------------------------------------------------------------
> > --
> > [INFO] BUILD FAILURE
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [INFO] Total time: 3:00.671s
> > [INFO] Finished at: Sat Jul 04 11:48:00 CST 2015 [INFO] Final Memory:
> > 54M/335M [INFO]
> > ----------------------------------------------------------------------
> > -- [ERROR] Failed to execute goal on project mavibot-backend: Could
> > not resolve dependencies for project
> > org.apache.kerby:mavibot-backend:jar:1.0-SNAPSHOT: Could not find
> > artifact org .apache.directory.mavibot:mavibot:jar:1.0.0-M8-SNAPSHOT
> > -> [Help 1]
> >
> you need latest mavibot build in your local repo
>
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with
> > the -e switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionE
> > xception
> > [ERROR]
> > [ERROR] After correcting the problems, you can resume the build with
> > the command
> > [ERROR] mvn <goals> -rf :mavibot-backend
> >
>
>
>
> --
> Kiran Ayyagari
> http://keydap.com
>
--
Kiran Ayyagari
http://keydap.com
RE: Kerby building fails
Posted by "Zheng, Kai" <ka...@intel.com>.
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.
Regards,
Kai
-----Original Message-----
From: Kiran Ayyagari [mailto:kayyagari@apache.org]
Sent: Saturday, July 04, 2015 1:15 PM
To: kerby@directory.apache.org
Subject: Re: Kerby building fails
On Sat, Jul 4, 2015 at 11:51 AM, Zheng, Kai <ka...@intel.com> wrote:
> Hi Kiran,
>
> It always fails on my side as below. Isn't the artifact already pushed
> to the public, or should we use any public available one? Thanks.
>
> Regards,
> Kai
>
> [INFO] Kerby Kdc Test .................................... SUCCESS
> [33.404s] [INFO] Mavibot based backend .............................
> FAILURE [0.022s] [INFO] Kerby Distribution
> ................................ SKIPPED [INFO] KDC Dist
> .......................................... SKIPPED [INFO] Tool Dist
> ......................................... SKIPPED [INFO] Kerby
> benchmark ................................... SKIPPED [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] BUILD FAILURE
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 3:00.671s
> [INFO] Finished at: Sat Jul 04 11:48:00 CST 2015 [INFO] Final Memory:
> 54M/335M [INFO]
> ----------------------------------------------------------------------
> -- [ERROR] Failed to execute goal on project mavibot-backend: Could
> not resolve dependencies for project
> org.apache.kerby:mavibot-backend:jar:1.0-SNAPSHOT: Could not find
> artifact org .apache.directory.mavibot:mavibot:jar:1.0.0-M8-SNAPSHOT
> -> [Help 1]
>
you need latest mavibot build in your local repo
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionE
> xception
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with
> the command
> [ERROR] mvn <goals> -rf :mavibot-backend
>
--
Kiran Ayyagari
http://keydap.com
Re: Kerby building fails
Posted by Kiran Ayyagari <ka...@apache.org>.
On Sat, Jul 4, 2015 at 11:51 AM, Zheng, Kai <ka...@intel.com> wrote:
> Hi Kiran,
>
> It always fails on my side as below. Isn't the artifact already pushed to
> the public, or should we use any public available one? Thanks.
>
> Regards,
> Kai
>
> [INFO] Kerby Kdc Test .................................... SUCCESS
> [33.404s]
> [INFO] Mavibot based backend ............................. FAILURE [0.022s]
> [INFO] Kerby Distribution ................................ SKIPPED
> [INFO] KDC Dist .......................................... SKIPPED
> [INFO] Tool Dist ......................................... SKIPPED
> [INFO] Kerby benchmark ................................... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 3:00.671s
> [INFO] Finished at: Sat Jul 04 11:48:00 CST 2015
> [INFO] Final Memory: 54M/335M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project mavibot-backend: Could not
> resolve dependencies for project
> org.apache.kerby:mavibot-backend:jar:1.0-SNAPSHOT: Could not find artifact
> org
> .apache.directory.mavibot:mavibot:jar:1.0.0-M8-SNAPSHOT -> [Help 1]
>
you need latest mavibot build in your local repo
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :mavibot-backend
>
--
Kiran Ayyagari
http://keydap.com