Fixed
Details
Details
Assignee
Marco Peters
Marco PetersReporter
Julien Malik
Julien MalikFix versions
Affects versions
Components
Priority
MajorCreated 9 December 2015 at 17:45
Updated 10 December 2015 at 14:34
Resolved 10 December 2015 at 14:34
Major
Steps to reproduce :
$ rm -rf $HOME/.m2/repository/org/esa/snap $ mvn clean install [INFO] Scanning for projects... [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.esa.snap:snap-desktop:3.0.0-SNAPSHOT (/home/jmalik/dev/src/senbox/senbox-org/master/snap-desktop/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.esa.snap:snap-engine:pom:3.0.0-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 6, 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/UnresolvableModelExceptionI expect in this situation that mvn starts downloading snap-engine modules from nexus, and builds snap-desktop on top of them.
One solution is probably to get rid of :
https://github.com/senbox-org/snap-desktop/blob/master/pom.xml#L6-L10
but then, this requires developers to
mvn installsnap-engine modules when developing because mvn picks up its dependencies only from the mvn local repository. (to be confirmed by BC that this is the cause).
This prevent travis-ci to build snap-desktop :
https://travis-ci.org/senbox-org/snap-desktop