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 <[email protected]>: > 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 <[email protected]>: >>> On Wed, Feb 9, 2011 at 9:04 PM, Fabian Christ >>> <[email protected]> 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 [email protected] > skype bluvale > > -- Fabian
