Stanbol
  1. Stanbol
  2. STANBOL-957

Cannot build Stanbol (Trunk) on Windows 8 / Maven 3.0.4

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.12.0
    • Component/s: Build
    • Labels:
      None
    • Environment:
      Windows 8, Maven 3.0.4,

      Description

      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?

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Oak Ninja
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development