Hi, Compiling the top level project (i.e. the reactor) will also compile the stable launcher. And compiling the stable launcher requires having compiled the odules first.
I'm surprised about the restlests I thought I had recently excluded this transitive dependendency. In the video on http://vimeo.com/61415903 I compile and run Stanbol, not encountering any problem on windows. I should be possible to do it the same way on ubuntu. Cheers, Reto On Fri, Jun 7, 2013 at 2:12 PM, David Wynter <david.wyn...@refinery29.com>wrote: > Hi, > > I realised now what my problem is, the instructions for the 3rd step should > read > > "Change your directory to stanbol/launchers/stable. Then run 'mvn clean > install'" > > However, since I had managed to fix the top level pom.xml to run, maybe > that is a prerequisite step to doing this install of the stable launcher? > > Regards, > > David > > > > > On Fri, Jun 7, 2013 at 12:05 PM, Rupert Westenthaler < > rupert.westentha...@gmail.com> wrote: > > > Hi David > > > > Our goal is to have a working build on any platform that provides Java > > 6+ and Maven 3. The only issue I am aware of are some unit test > > related issues under windows. So some windows users might be forced to > > skip tests for some modules. > > > > On Thu, Jun 6, 2013 at 3:49 PM, David Wynter > > <david.wyn...@refinery29.com> wrote: > > > Hi, > > > > > > I followed the instruction here. > > > http://stanbol.apache.org/docs/trunk/tutorial.html > > > > > > With one exception, where it says "From the source directory run", 3rd > > > step, I assume you meant from the stanbol top level directory, where > the > > > top level pom.xml resides. > > > > > > After this the "mvn clean install" fails, firstly because there is a > solr > > > dependency on 2 restlet jars, discussed on this list at length, here > > > > > > http://mail-archives.apache.org/mod_mbox/stanbol-dev/201304.mbox/%3ccaa7lao26hskuvrxsj2hrz+a2hxhi0hacmeipkhv-xttuzm+...@mail.gmail.com%3E > > > > AFAIK reto removed the restlet dependencies in > > http://svn.apache.org/r1481832. So you should not need those to build > > stanbol. > > > > Reto can you confirm this? > > > > > > > > ( so why have a broken pom.xml in your distribution that does not > > address > > > the problem!?) Searched for an answer, found one here - > > > http://restlet.org/download/maven, but neither approach worked for me > so > > > ended up copying the jar files to my local repository, that worked. > > > > > > Then finally I needed to find and download the opennlp dependency on > > jwnl. > > > Then ran this command to add to my local repository > > > > > > mvn deploy:deploy-file -DgroupId=jwnl -DartifactId=jwnl -Dversion=1.3.3 > > > -Dfile=/home/david/jwnl-1.3.3.jar -Dpackaging=jar > > > -Durl=file:///home/david/.m2/repository. > > > > > > > Actually that true." jwnl:jwnl:1.3.3" is not in maven central. No Idea > > why I have never noticed that. My local Maven repository claims that > > it retrieved this file via > > > > http\://opennlp.sourceforge.net/maven2/.lastUpdated=1351889296751 > > http\://repo.maven.apache.org/maven2/.lastUpdated=1351889295449 > > > > However I noticed that the most current release of OpenNLP now uses > > "net.sf.jwordnet:jwnl:jar:1.3.3" and this dependency is available in > > maven central. I will create an issue to upgrade to OpenNLP 1.5.3 > > > > Thanks for reporting this! > > > > best > > Rupert > > > > > > > Now it builds. > > > > > > So are my experiences normal or is the maven install broken? If this is > > > common then hopefully this helps someone going thru the same > experience. > > > > > > Thanks, > > > > > > David > > > > > > > > -- > > | Rupert Westenthaler rupert.westentha...@gmail.com > > | Bodenlehenstraße 11 ++43-699-11108907 > > | A-5500 Bischofshofen > > >
