Hi,

this is caused by a recent change of the version numbering in the
Apache Stanbol parent POM. Looks like this module was not updated to
the new scheme. I have already committed a fix - so it should work now

best
Rupert

On Sat, Aug 18, 2012 at 11:31 PM, kritarth anand
<[email protected]> wrote:
> Hi,
>
> I have been trying to run the a demo ehealth to try and configure it with
> my engine. But I am not able to run it. I tried running it, running mvn
> install throws this error
>
> sk@ubuntu:~/stanbol/demos/ehealth$ mvn install
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project
> org.apache.stanbol:org.apache.stanbol.demo.ehealth:0.10.0-incubating-SNAPSHOT
> (/home/jsk/stanbol/demos/ehealth/pom.xml) has 1 error
> [ERROR]     Non-resolvable parent POM: Could not find artifact
> org.apache.stanbol:stanbol-parent:pom:0.10.0-incubating-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 16, column 11 ->
> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [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 read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
> The error shouldn't occur as the parent pom does exist. I checked. Please
> let me know if some one has leads on this.
>
> Kritarth



-- 
| Rupert Westenthaler             [email protected]
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Reply via email to