[
https://issues.apache.org/jira/browse/STANBOL-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585819#comment-13585819
]
Rupert Westenthaler commented on STANBOL-957:
---------------------------------------------
Hi
> C:\Dev\Stanbol\commons\web\sparql\target\classes (Access is denied)
This looks like a specific issue of your environment. But in any case it is
very strange:
(1) because I would not expect that the Apache Sling maven-launchpad-plugin
accesses '\target\classes' but rather '\target'
(2) because you are getting an 'Access is denied' error, suggesting that the
user does not have access to this directory that is created by the same maven
build process.
(2b) does this folder exist?
There should be also some information about the error above the "[INFO] Reactor
Summary:" included in your comment. Do those lines contain additional
informations?
Does the same error appear if you call
mvn clean install -rf :org.apache.stanbol.launchers.full
Maybe this woks as in that case the bundle should be located via the local
maven repository and not via modules included by the same maven command.
> 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
>
> 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
