[
https://issues.apache.org/jira/browse/STANBOL-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587445#comment-13587445
]
Rupert Westenthaler commented on STANBOL-957:
---------------------------------------------
This is now because of STANBOL-811
Caused by: org.apache.lucene.index.IndexNotFoundException: no segments* file
found in
org.apache.lucene.store.SimpleFSDirectory@C:\Users\Esse\AppData\Local\Temp\stanbol-evaluation-folder-9016199723602145004.tmp\evaluationclassifierserver\default-topic-model\data\index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@1591b4d: files:
[_b.fdt, _b.fdx, _b.frq, _b.prx, _b.tis, _b.tvd, _b.tvf, _b.tvx]
clearly suggests that my patch for STANBOL-811 (revision
http://svn.apache.org/r1449609) has not removed all creations of temp files as
the path in the exception still suggests that files within the Windows temp
folder are missing.
> Cannot build Stanbol (Trunk) on Windows 8 / Maven 3.0.4
> -------------------------------------------------------
>
> Key: STANBOL-957
> URL: https://issues.apache.org/jira/browse/STANBOL-957
> Project: Stanbol
> Issue Type: Bug
> Components: Build
> Environment: Windows 8, Maven 3.0.4,
> Reporter: Oak Ninja
> Priority: Blocker
> Attachments:
> org.apache.stanbol.entityhub.indexing.source.jenatdb.RdfIndexingSourceTest.txt,
> surefire_reportsR1450112_win8_centos6.3.zip, topic_engine-build.log
>
>
> Hi!
> Following the Getting Started guide at
> http://stanbol.apache.org/docs/trunk/tutorial.html, my build fails with the
> following error:
> C:\lib\stanbol>mvn clean install
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project
> org.apache.stanbol:apache-stanbol-enhancement-engines:0.10
> .1-SNAPSHOT (C:\lib\stanbol\enhancement-engines\pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact
> org.apache.stanbo
> l:stanbol-parent:pom:4-SNAPSHOT and 'parent.relativePath' points at wrong
> local
> POM @ line 21, column 11 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> swit
> ch.
> [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
> rea
> d the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildin
> gException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableMo
> delException
> C:\lib\stanbol>
> So i tried resolving it by changing the relative path in the affected pom
> from
> <parent>
> <groupId>org.apache.stanbol</groupId>
> <artifactId>stanbol-parent</artifactId>
> <version>4-SNAPSHOT</version>
> </parent>
> to
> <parent>
> <groupId>org.apache.stanbol</groupId>
> <artifactId>stanbol-parent</artifactId>
> <version>4-SNAPSHOT</version>
> <relativePath>../parent/pom.xml</relativePath>
> </parent>
> and that resolved the specific error, but the next build attempt were
> followed by the same error in the following pom and i'm thinking i'm missing
> something trivial here - all the project's paths cannot be erronous, right?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
