search

WingLongitude / lontra-harvester

Lontra is a tool used as a Harvester to ingest biodiversity data
MIT License
1 stars 3 forks source link

Compilation error #34

Closed dvdscripter closed 8 years ago

dvdscripter commented 8 years ago

Tried in two distributions.

dvd@sibbr:~/src/lontra-harvester$ mvn -version
Apache Maven 3.0.5
Maven home: /usr/share/maven
Java version: 1.7.0_91, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.19.0-25-generic", arch: "amd64", family: "unix"
dvd@sibbr:~/src/lontra-harvester$ mvn clean package
[INFO] Scanning for projects...
Downloading: http://repository.gbif.org/content/groups/gbif/winglongitude/winglongitude-lontra/1.3-SNAPSHOT/maven-metadata.xml
Downloading: http://repository.gbif.org/content/groups/gbif/winglongitude/winglongitude-lontra/1.3-SNAPSHOT/winglongitude-lontra-1.3-SNAPSHOT.pom
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project winglongitude:dist:1.3-SNAPSHOT (/home/dvd/src/lontra-harvester/dist/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not find artifact winglongitude:winglongitude-lontra:pom:1.3-SNAPSHOT in gbif-all (http://repository.gbif.org/content/groups/gbif) and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [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
cgendreau commented 8 years ago

The build has been left in a non-stable state, this should not happen:

https://travis-ci.org/WingLongitude/lontra-harvester/builds

cgendreau commented 8 years ago

version in the pom should not be edited manually, mvn release:update-versions -DautoVersionSubmodules=true should always be used to avoid this kind of issues.