​Thanks, this worked.

For anyone else who may have a problem similar to this, here (
https://stackoverflow.com/a/37068864/8236733) is a bit of info on what is
going on with maven here.
The main info in the SO post is...

>
> In order to resolve the parent project, these possible sources are checked:


> - relativePath

- local repository

- remote repositories


> The relative path, if not given explicitly, defaults to `..`, i.e. the pom
> in the parent directory of the current project. So Maven checks whether a)
> there is a pom file in that directory and b) that pom file contains the
> same coordinates as stated in the parent definition of the current project.


> If a) and b) are true, that pom file is used as the parent for the
> resolving of the effective pom.


> If a) is true, and b) is false, a warning is given, because this usually
> points to a misconfigured project (as in your case) adn the pom is ignored.


> If a) is false, the other sources are checked.

​
>

​Furthermore, for people having install/build issues, you may also
encounter an error message talking about missing dependencies, eg.

​....
>
[INFO] Apache Atlas Distribution 1.0.0-SNAPSHOT ........... SKIPPED

[INFO]
> ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO]
> ------------------------------------------------------------------------

[INFO] Total time: 49:02 min

[INFO] Finished at: 2018-04-07T13:57:10-10:00

[INFO]
> ------------------------------------------------------------------------

[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (verify) on
> project atlas-webapp: There are test failures.

​...​.


​For such an issue, this SO post (
https://stackoverflow.com/a/13173440/8236733) was also helpful​. Basically,
just try running "mvn dependency::tree" before running mvn clean
-DskipTests install.



On Sat, Apr 7, 2018 at 10:36 AM, Madhan Neethiraj <mad...@apache.org> wrote:

> Ashutosh – this might require addition of ‘relativePath’ in
> tools/atlas-migration-exporter/pom.xml, as shown below. Can you please
> review and update?
>
>
>
>     <parent>
>
>         <groupId>org.apache.atlas</groupId>
>
>         <artifactId>apache-atlas</artifactId>
>
>         <version>1.0.0-SNAPSHOT</version>
>
>         <relativePath>../../</relativePath>
>
>     </parent>
>
>
>
>
>
> Thanks,
>
> Madhan
>
>
>
>
>
>
>
> *From: *Reed Villanueva <villanuevar...@gmail.com>
> *Reply-To: *"user@atlas.apache.org" <user@atlas.apache.org>
> *Date: *Saturday, April 7, 2018 at 5:52 AM
> *To: *"user@atlas.apache.org" <user@atlas.apache.org>
> *Subject: *Atlas master fails to build, [FATAL] Non-resolvable parent POM
>
>
>
> Following the instructions on the atlas installation docs (
> https://atlas.apache.org/InstallationSteps.html), I get the following
> error:
>
>
>
> ➜  atlas git:(master)# mvn clean install
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for org.apache.atlas:atlas-
> migration-exporter:[unknown-version]: Could not find artifact
> org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.apache.solr:solr-solrj:jar -> version (?) vs
> ${solr.version} @ org.apache.atlas:atlas-graphdb-titan0:[unknown-version],
> /home/reedv/atlas/graphdb/titan0/pom.xml, line 194, column 21
> ......
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project 
> org.apache.atlas:atlas-migration-exporter:[unknown-version]
> (/home/me/atlas/tools/atlas-migration-exporter/pom.xml) has 1 error
> [ERROR]     Non-resolvable parent POM for org.apache.atlas:atlas-
> migration-exporter:[unknown-version]: Could not find artifact
> org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13 ->
> [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
>
>
>
>
>
> Some googling shows that this could be caused by a pom file that is not
> properly/fully listing dependencies (https://issues.apache.org/
> jira/browse/ATLAS-1106). However, I do not work with maven often, so if
> someone could educate me about what is really happening here with the pom
> file and what can be done about it, I would appreciate it. Thanks.
>
>
>

Reply via email to