On Feb 10, 2011, at 9:20 AM, Bertrand Delacretaz wrote: > Hi Valentina, > > On Wed, Feb 9, 2011 at 11:19 PM, valentina presutti > <[email protected]> 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."
