You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Olivier Grisel <ol...@ensta.org> on 2011/02/09 19:47:25 UTC
Missing dependency when building stanbol
Hi all,
I have trying to build the current stanbol tree from the top level. I
have manually added the missing owlapi / owl-link and hermit jar as
mentionned in the toplevel README file but I still get the following
error message:
Missing:
----------
1) eu.iksproject:eu.iksproject.kres.shared.dependency.owlapi:jar:0.7
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=eu.iksproject
-DartifactId=eu.iksproject.kres.shared.dependency.owlapi -Dversion=0.7
-Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=eu.iksproject
-DartifactId=eu.iksproject.kres.shared.dependency.owlapi -Dversion=0.7
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) eu.iksproject:eu.iksproject.kres.ontologies:bundle:0.7
2) eu.iksproject:eu.iksproject.kres.shared.dependency.owlapi:jar:0.7
Could someone update the toplevel README to make sure stanbol is
buildable at any time?
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
Re: Missing dependency when building stanbol
Posted by Stefane Fermigier <sf...@nuxeo.com>.
On Feb 10, 2011, at 9:20 AM, Bertrand Delacretaz wrote:
> Hi Valentina,
>
> On Wed, Feb 9, 2011 at 11:19 PM, valentina presutti
> <va...@cnr.it> wrote:
>> Thanks Fabian, it was clear indeed.
>> What I meant is that if it's a matter of the failing tests maybe it's enough to fix them (and I believe we
>> need to be more careful before committing next times)....
>
> The main problem with the kres build is that it requires running a
> script to install jars in the local Maven repository
> (see https://svn.apache.org/repos/asf/incubator/stanbol/trunk/kres/README.txt).
> This won't work in a Hudson build (https://hudson.apache.org) which I
> hope to setup soon.
You mean, "Jenkins", I hope.
>
>> Licensing shouldn't be an issue at the moment...btw, we're working also for that, but unfortunately it does not
>> depend only on us :(
>
> It is an issue in that it prevents us from releasing kres - until
> that's fixed, as I said I'm +1 on disabling kres temporarily in the
> default build. People working on it can reactivate the kres build
> using a simple mvn -P option.
+ 1.
Getting the build automated should be the priority. I remember complaining about it 6 months ago if not more.
S.
--
Stefane Fermigier, Founder and Chairman, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com/ - +33 1 40 33 79 87 - http://twitter.com/sfermigier
Join the Nuxeo Group on LinkedIn: http://linkedin.com/groups?gid=43314
New Nuxeo release: http://nuxeo.com/dm54
"There's no such thing as can't. You always have a choice."
Re: Missing dependency when building stanbol
Posted by Enrico Daga <en...@gmail.com>.
Dear All,
> I think we should comment the kres reference in the toplevel pom.xml
> in the mean time and re-enable it as soon as Enrico or someone else
> tells me which jars to upload to the nuxeo maven repo and that we have
> tested that the toplevel build is fully functional without any manual
> operation. Also I don't want to upload those 3 jars twice under
> different names, so there might have non trivial changes to do in the
> kres build config (I am not sure what the shared-dependency variant
> stands for).
+1 for this temporary solution.
I think is the best solution now. This decouple the problems, at least.
Then we will move on solving the issues one by one. @Olivier. We will
come back to you and perform any necessary changes on the kres code to
avoid manual install of bundles.
I am not familiar with hudson and I did not perceived the manual
install of libraries as a blocking issue.
Anyway, we will fix this and the other kres-related issues soon, most
of them are already solved in other kres forks (for instance the wrong
dependencies in the pom files have been fixed for integrate kres in
another IKS activity.
Unfortunately the most of the kres code has been written bu
Alessandro, Andrea and Elvio, which only recently are going to become
committers.
Hope this clarifies the situation from our side.
Enrico
On 10 February 2011 10:40, Olivier Grisel <ol...@ensta.org> wrote:
> 2011/2/10 Bertrand Delacretaz <bd...@apache.org>:
>> Hi Valentina,
>>
>> On Wed, Feb 9, 2011 at 11:19 PM, valentina presutti
>> <va...@cnr.it> wrote:
>>> Thanks Fabian, it was clear indeed.
>>> What I meant is that if it's a matter of the failing tests maybe it's enough to fix them (and I believe we
>>> need to be more careful before committing next times)....
>>
>> The main problem with the kres build is that it requires running a
>> script to install jars in the local Maven repository
>> (see https://svn.apache.org/repos/asf/incubator/stanbol/trunk/kres/README.txt).
>> This won't work in a Hudson build (https://hudson.apache.org) which I
>> hope to setup soon.
>
> Yes this is the real deal.
>
> Also when I checkout a new java project for evaluation and I see a
> toplevel pom.xml I expect that a single "mvn install" or "mvn
> assembly:assembly" will get me up and running. Having to manually
> install jars makes me a sad, sad panda.
>
> The fact that those jars are not licensed under an ASF compliant make
> us not able to push them on the official ASF mvn repository. I can
> update the 3 documented jars on the nuxeo vendors repository as a
> temporary solution but the one dependency that is not documented, I
> don't know how to handle it.
>
> I think we should comment the kres reference in the toplevel pom.xml
> in the mean time and re-enable it as soon as Enrico or someone else
> tells me which jars to upload to the nuxeo maven repo and that we have
> tested that the toplevel build is fully functional without any manual
> operation. Also I don't want to upload those 3 jars twice under
> different names, so there might have non trivial changes to do in the
> kres build config (I am not sure what the shared-dependency variant
> stands for).
>
>>> Licensing shouldn't be an issue at the moment...btw, we're working also for that, but unfortunately it does not
>>> depend only on us :(
>>
>> It is an issue in that it prevents us from releasing kres - until
>> that's fixed, as I said I'm +1 on disabling kres temporarily in the
>> default build. People working on it can reactivate the kres build
>> using a simple mvn -P option.
>
> Or they can just cd into the kres folder and build from there (after
> installing the missing jars manually).
>
> --
> Olivier
> http://twitter.com/ogrisel - http://github.com/ogrisel
>
--
Enrico Daga
--
http://www.enridaga.net
skype: enri-pan
Re: Missing dependency when building stanbol
Posted by Olivier Grisel <ol...@ensta.org>.
2011/2/10 Bertrand Delacretaz <bd...@apache.org>:
> Hi Valentina,
>
> On Wed, Feb 9, 2011 at 11:19 PM, valentina presutti
> <va...@cnr.it> wrote:
>> Thanks Fabian, it was clear indeed.
>> What I meant is that if it's a matter of the failing tests maybe it's enough to fix them (and I believe we
>> need to be more careful before committing next times)....
>
> The main problem with the kres build is that it requires running a
> script to install jars in the local Maven repository
> (see https://svn.apache.org/repos/asf/incubator/stanbol/trunk/kres/README.txt).
> This won't work in a Hudson build (https://hudson.apache.org) which I
> hope to setup soon.
Yes this is the real deal.
Also when I checkout a new java project for evaluation and I see a
toplevel pom.xml I expect that a single "mvn install" or "mvn
assembly:assembly" will get me up and running. Having to manually
install jars makes me a sad, sad panda.
The fact that those jars are not licensed under an ASF compliant make
us not able to push them on the official ASF mvn repository. I can
update the 3 documented jars on the nuxeo vendors repository as a
temporary solution but the one dependency that is not documented, I
don't know how to handle it.
I think we should comment the kres reference in the toplevel pom.xml
in the mean time and re-enable it as soon as Enrico or someone else
tells me which jars to upload to the nuxeo maven repo and that we have
tested that the toplevel build is fully functional without any manual
operation. Also I don't want to upload those 3 jars twice under
different names, so there might have non trivial changes to do in the
kres build config (I am not sure what the shared-dependency variant
stands for).
>> Licensing shouldn't be an issue at the moment...btw, we're working also for that, but unfortunately it does not
>> depend only on us :(
>
> It is an issue in that it prevents us from releasing kres - until
> that's fixed, as I said I'm +1 on disabling kres temporarily in the
> default build. People working on it can reactivate the kres build
> using a simple mvn -P option.
Or they can just cd into the kres folder and build from there (after
installing the missing jars manually).
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
Re: Missing dependency when building stanbol
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Valentina,
On Wed, Feb 9, 2011 at 11:19 PM, valentina presutti
<va...@cnr.it> wrote:
> Thanks Fabian, it was clear indeed.
> What I meant is that if it's a matter of the failing tests maybe it's enough to fix them (and I believe we
> need to be more careful before committing next times)....
The main problem with the kres build is that it requires running a
script to install jars in the local Maven repository
(see https://svn.apache.org/repos/asf/incubator/stanbol/trunk/kres/README.txt).
This won't work in a Hudson build (https://hudson.apache.org) which I
hope to setup soon.
> Licensing shouldn't be an issue at the moment...btw, we're working also for that, but unfortunately it does not
> depend only on us :(
It is an issue in that it prevents us from releasing kres - until
that's fixed, as I said I'm +1 on disabling kres temporarily in the
default build. People working on it can reactivate the kres build
using a simple mvn -P option.
-Bertrand
Re: Missing dependency when building stanbol
Posted by valentina presutti <va...@cnr.it>.
Thanks Fabian, it was clear indeed.
What I meant is that if it's a matter of the failing tests maybe it's enough to fix them (and I believe we need to be more careful before committing next times).
Licensing shouldn't be an issue at the moment...btw, we're working also for that, but unfortunately it does not depend only on us :(
Val
On Feb 9, 2011, at 11:14 PM, Fabian Christ wrote:
> Hi,
>
> just to be clear. This is _not_ about removing KReS from Stanbol. It
> is just to remove it from the default build process. Everyone who
> wants to use KReS will be able to.
>
> - Fabian
>
> 2011/2/9 valentina presutti <va...@cnr.it>:
>> Hi all,
>>
>> although I think it's a good idea to have profiles (why don't we have them for the whole package +/-KReS, +/- RICK, etc.?)
>> are we sure it's a good idea to remove KReS until licensing issues are not solved?
>>
>> While testing have to be fixed, we can live with licensing while we solve them (as long as we are in incubation), is that correct?
>> Possible adjustments to KReS (if licenses do not change) could rely on a community effort, if KReS is removed I am concerned this will be much harder to realize.
>>
>> Btw, I am sure Enrico will handle the testing issue asap.
>>
>> Val
>>
>> On Feb 9, 2011, at 9:38 PM, Fabian Christ wrote:
>>
>>> 2011/2/9 Bertrand Delacretaz <bd...@apache.org>:
>>>> On Wed, Feb 9, 2011 at 9:04 PM, Fabian Christ
>>>> <ch...@googlemail.com> wrote:
>>>>> ...Another question/solution: Should we remove KReS from the build
>>>>> process until the KReS related issues regarding licensing, failing
>>>>> tests, and renaming are solved? Personally, I do not know exactly what
>>>>> to do with KReS in its current state....
>>>>
>>>> +1 to disabling the kres build by default, using a Maven profile.
>>>
>>> Just to be clear. What you mean is to create a profile 'withKres' and
>>> only if this profile is active the KReS build is triggered?
>>>
>>> +1 for that and I can do this tomorrow.
>>>
>>>> We probably need this to be able to configure automated builds with Hudson.
>>>
>>> Indeed.
>>>
>>> --
>>> Fabian
>>
>>
>> ------------------------------------------------------------
>>
>> Valentina Presutti
>> Semantic Technology Laboratory (STLab)
>> Institute for Cognitive Science and Technology (ISTC)
>> National Research Council (CNR)
>> Via Nomentana 56, Rome - Italy
>>
>> icq# 122838754
>> msn vpresutti@hotmail.it
>> skype bluvale
>>
>>
>
>
>
> --
> Fabian
------------------------------------------------------------
Valentina Presutti
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, Rome - Italy
icq# 122838754
msn vpresutti@hotmail.it
skype bluvale
Re: Missing dependency when building stanbol
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
just to be clear. This is _not_ about removing KReS from Stanbol. It
is just to remove it from the default build process. Everyone who
wants to use KReS will be able to.
- Fabian
2011/2/9 valentina presutti <va...@cnr.it>:
> Hi all,
>
> although I think it's a good idea to have profiles (why don't we have them for the whole package +/-KReS, +/- RICK, etc.?)
> are we sure it's a good idea to remove KReS until licensing issues are not solved?
>
> While testing have to be fixed, we can live with licensing while we solve them (as long as we are in incubation), is that correct?
> Possible adjustments to KReS (if licenses do not change) could rely on a community effort, if KReS is removed I am concerned this will be much harder to realize.
>
> Btw, I am sure Enrico will handle the testing issue asap.
>
> Val
>
> On Feb 9, 2011, at 9:38 PM, Fabian Christ wrote:
>
>> 2011/2/9 Bertrand Delacretaz <bd...@apache.org>:
>>> On Wed, Feb 9, 2011 at 9:04 PM, Fabian Christ
>>> <ch...@googlemail.com> wrote:
>>>> ...Another question/solution: Should we remove KReS from the build
>>>> process until the KReS related issues regarding licensing, failing
>>>> tests, and renaming are solved? Personally, I do not know exactly what
>>>> to do with KReS in its current state....
>>>
>>> +1 to disabling the kres build by default, using a Maven profile.
>>
>> Just to be clear. What you mean is to create a profile 'withKres' and
>> only if this profile is active the KReS build is triggered?
>>
>> +1 for that and I can do this tomorrow.
>>
>>> We probably need this to be able to configure automated builds with Hudson.
>>
>> Indeed.
>>
>> --
>> Fabian
>
>
> ------------------------------------------------------------
>
> Valentina Presutti
> Semantic Technology Laboratory (STLab)
> Institute for Cognitive Science and Technology (ISTC)
> National Research Council (CNR)
> Via Nomentana 56, Rome - Italy
>
> icq# 122838754
> msn vpresutti@hotmail.it
> skype bluvale
>
>
--
Fabian
Re: Missing dependency when building stanbol
Posted by valentina presutti <va...@cnr.it>.
Hi all,
although I think it's a good idea to have profiles (why don't we have them for the whole package +/-KReS, +/- RICK, etc.?)
are we sure it's a good idea to remove KReS until licensing issues are not solved?
While testing have to be fixed, we can live with licensing while we solve them (as long as we are in incubation), is that correct?
Possible adjustments to KReS (if licenses do not change) could rely on a community effort, if KReS is removed I am concerned this will be much harder to realize.
Btw, I am sure Enrico will handle the testing issue asap.
Val
On Feb 9, 2011, at 9:38 PM, Fabian Christ wrote:
> 2011/2/9 Bertrand Delacretaz <bd...@apache.org>:
>> On Wed, Feb 9, 2011 at 9:04 PM, Fabian Christ
>> <ch...@googlemail.com> wrote:
>>> ...Another question/solution: Should we remove KReS from the build
>>> process until the KReS related issues regarding licensing, failing
>>> tests, and renaming are solved? Personally, I do not know exactly what
>>> to do with KReS in its current state....
>>
>> +1 to disabling the kres build by default, using a Maven profile.
>
> Just to be clear. What you mean is to create a profile 'withKres' and
> only if this profile is active the KReS build is triggered?
>
> +1 for that and I can do this tomorrow.
>
>> We probably need this to be able to configure automated builds with Hudson.
>
> Indeed.
>
> --
> Fabian
------------------------------------------------------------
Valentina Presutti
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, Rome - Italy
icq# 122838754
msn vpresutti@hotmail.it
skype bluvale
Re: Missing dependency when building stanbol
Posted by Fabian Christ <ch...@googlemail.com>.
+1
2011/2/10 Bertrand Delacretaz <bd...@apache.org>:
> On Wed, Feb 9, 2011 at 9:38 PM, Fabian Christ
> <ch...@googlemail.com> wrote:
>> 2011/2/9 Bertrand Delacretaz <bd...@apache.org>:
>>...
>>> +1 to disabling the kres build by default, using a Maven profile.
>>
>> Just to be clear. What you mean is to create a profile 'withKres' and
>> only if this profile is active the KReS build is triggered?
>>
>> +1 for that and I can do this tomorrow.
>
> I had to do it already for STANBOL-70, we can revert once the kres
> build works without manual intervention.
>
> -Bertrand
>
--
Fabian
Re: Missing dependency when building stanbol
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Feb 9, 2011 at 9:38 PM, Fabian Christ
<ch...@googlemail.com> wrote:
> 2011/2/9 Bertrand Delacretaz <bd...@apache.org>:
>...
>> +1 to disabling the kres build by default, using a Maven profile.
>
> Just to be clear. What you mean is to create a profile 'withKres' and
> only if this profile is active the KReS build is triggered?
>
> +1 for that and I can do this tomorrow.
I had to do it already for STANBOL-70, we can revert once the kres
build works without manual intervention.
-Bertrand
Re: Missing dependency when building stanbol
Posted by Fabian Christ <ch...@googlemail.com>.
2011/2/9 Bertrand Delacretaz <bd...@apache.org>:
> On Wed, Feb 9, 2011 at 9:04 PM, Fabian Christ
> <ch...@googlemail.com> wrote:
>> ...Another question/solution: Should we remove KReS from the build
>> process until the KReS related issues regarding licensing, failing
>> tests, and renaming are solved? Personally, I do not know exactly what
>> to do with KReS in its current state....
>
> +1 to disabling the kres build by default, using a Maven profile.
Just to be clear. What you mean is to create a profile 'withKres' and
only if this profile is active the KReS build is triggered?
+1 for that and I can do this tomorrow.
> We probably need this to be able to configure automated builds with Hudson.
Indeed.
--
Fabian
Re: Missing dependency when building stanbol
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Feb 9, 2011 at 9:04 PM, Fabian Christ
<ch...@googlemail.com> wrote:
> ...Another question/solution: Should we remove KReS from the build
> process until the KReS related issues regarding licensing, failing
> tests, and renaming are solved? Personally, I do not know exactly what
> to do with KReS in its current state....
+1 to disabling the kres build by default, using a Maven profile.
We probably need this to be able to configure automated builds with Hudson.
-Bertrand
Re: Missing dependency when building stanbol
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
yes I had the same problem. But I don't understand why this happens.
During the build process the artifact
eu.iksproject:eu.iksproject.kres.shared.dependency.owlapi:jar:0.7 is
built but for some reason not installed in the local repository. When
I build KReS from the kres folder, the artifact is built and installed
correctly in the local repo.
My observation is that we have different behavior in the build process
if KReS is built on its own or as part of the overall Stanbol build.
As I said - I could not figure out yet why this happens.
Another question/solution: Should we remove KReS from the build
process until the KReS related issues regarding licensing, failing
tests, and renaming are solved? Personally, I do not know exactly what
to do with KReS in its current state.
Best,
- Fabian
2011/2/9 Olivier Grisel <ol...@ensta.org>:
> Hi all,
>
> I have trying to build the current stanbol tree from the top level. I
> have manually added the missing owlapi / owl-link and hermit jar as
> mentionned in the toplevel README file but I still get the following
> error message:
>
> Missing:
> ----------
> 1) eu.iksproject:eu.iksproject.kres.shared.dependency.owlapi:jar:0.7
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=eu.iksproject
> -DartifactId=eu.iksproject.kres.shared.dependency.owlapi -Dversion=0.7
> -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=eu.iksproject
> -DartifactId=eu.iksproject.kres.shared.dependency.owlapi -Dversion=0.7
> -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) eu.iksproject:eu.iksproject.kres.ontologies:bundle:0.7
> 2) eu.iksproject:eu.iksproject.kres.shared.dependency.owlapi:jar:0.7
>
> Could someone update the toplevel README to make sure stanbol is
> buildable at any time?
>
> --
> Olivier
> http://twitter.com/ogrisel - http://github.com/ogrisel
>
--
Fabian