'parent.relativePath' of POM org.geonetwork-opensource:schema-sensorML:3.2.1-SNAPSHOT (…/git/core-geonetwork/schemas/sensorML/pom.xml) points at org.geonetwork-opensource.schemas:schemas instead of org.geonetwork-opensource:schemas

[LM-HZG]

Hello,

I'm having issues implementing this plugin into a fresh build of geonetwork. I could build it successfully without this submodule:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for GeoNetwork opensource 3.11.0-SNAPSHOT:
[INFO] 
[INFO] GeoNetwork opensource .............................. SUCCESS [ 11.333 s]
[INFO] common utils ....................................... SUCCESS [ 25.118 s]
[INFO] Caching xslt module ................................ SUCCESS [  0.107 s]
[INFO] ArcSDE module (dummy-api) .......................... SUCCESS [  0.156 s]
[INFO] GeoNetwork domain .................................. SUCCESS [01:58 min]
[INFO] Oaipmh modules ..................................... SUCCESS [  0.196 s]
[INFO] GeoNetwork Events .................................. SUCCESS [  0.139 s]
[INFO] GeoNetwork schema plugins .......................... SUCCESS [  0.010 s]
[INFO] GeoNetwork schema plugins core ..................... SUCCESS [ 24.133 s]
[INFO] GeoNetwork schema plugin for ISO19139/119 standards  SUCCESS [ 16.995 s]
[INFO] GeoNetwork index using Elasticsearch ............... SUCCESS [  0.012 s]
[INFO] GeoNetwork index Elasticsearch client .............. SUCCESS [ 12.140 s]
[INFO] GeoNetwork core .................................... SUCCESS [04:48 min]
[INFO] GeoNetwork Events .................................. SUCCESS [  0.295 s]
[INFO] GeoNetwork schema plugin for Dublin Core records retrieved by CSW SUCCESS [  0.071 s]
[INFO] GeoNetwork schema plugin for Dublin Core standard .. SUCCESS [  0.144 s]
[INFO] GeoNetwork schema plugin for ISO19110 standard ..... SUCCESS [  0.167 s]
[INFO] GeoNetwork schema plugin for ISO19115-3:2018 standard SUCCESS [ 53.708 s]
[INFO] GeoNetwork CSW server .............................. SUCCESS [  0.700 s]
[INFO] GeoNetwork harvesters .............................. SUCCESS [  5.497 s]
[INFO] GeoNetwork health monitor .......................... SUCCESS [  0.335 s]
[INFO] GeoNetwork Digital Object Identifier (DOI) client .. SUCCESS [  0.247 s]
[INFO] GeoNetwork services ................................ SUCCESS [ 53.604 s]
[INFO] Geonetwork Web Resources 4 Java .................... SUCCESS [01:57 min]
[INFO] GeoNetwork INSPIRE Atom ............................ SUCCESS [  0.933 s]
[INFO] GeoNetwork dashboard app based on Kibana ........... SUCCESS [  0.030 s]
[INFO] Release module ..................................... SUCCESS [  0.028 s]
[INFO] messaging .......................................... SUCCESS [01:29 min]
[INFO] workers ............................................ SUCCESS [  0.014 s]
[INFO] WFS features harvester ............................. SUCCESS [ 57.544 s]
[INFO] GeoNetwork Slave ................................... SUCCESS [  0.233 s]
[INFO] Tests for schema plugins ........................... SUCCESS [  0.412 s]
[INFO] GeoNetwork user interface module ................... SUCCESS [ 52.605 s]
[INFO] GeoNetwork Web module .............................. SUCCESS [02:47 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  18:19 min
[INFO] Finished at: 2020-09-10T16:37:54+01:00
[INFO] ------------------------------------------------------------------------

However, if I follow the given instructions:

cd schemas
git submodule add https://github.com/metadata101/sensorML.git sensorML

… I am confronted with the following error message:

You need to run this command from the toplevel of the working tree.

When I did that it worked, but the pulled subdirectory sensorML is located in core-geonetwork rather than schemas/ -- as one would expect. So I moved it to schemas/ manually, made the required changes to schemas/pom.xml and web/pom.xml and retried the compilation. Bu now I am confronted with the following error:

mvn clean install -DskipTests
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'parent.relativePath' of POM org.geonetwork-opensource:schema-sensorML:3.2.1-SNAPSHOT (/home/user/git/core-geonetwork/schemas/sensorML/pom.xml) points at org.geonetwork-opensource.schemas:schemas instead of org.geonetwork-opensource:schemas, please verify your project structure @ line 5, column 11
[FATAL] Non-resolvable parent POM for org.geonetwork-opensource:schema-sensorML:3.2.1-SNAPSHOT: Could not find artifact org.geonetwork-opensource:schemas:pom:3.2.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 5, column 11
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-assembly-plugin @ line 68, column 15
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.geonetwork-opensource:schema-sensorML:3.2.1-SNAPSHOT (/home/user/git/core-geonetwork/schemas/sensorML/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.geonetwork-opensource:schema-sensorML:3.2.1-SNAPSHOT: Could not find artifact org.geonetwork-opensource:schemas:pom:3.2.1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 5, 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

Any ideas?

[LM-HZG]

Anyone?

My group is on the brink of deciding which metadate cataloguing system we are going to use for our environmental data from the marine and coastal domain in the future (i.e. 10-20 years). And GN appears to be such a promising candidate according to our first impressions and tests. Simply great work of @fxprunayre et. al !

However, sensorML is one of the key requirements (besides ES indexing and a working csw-t interface) for our use case. And now I am wondering what my chances are to bring all these required features together to convince my superiors.
Any advice or feedback would be highly appreciated.

@Delawen Is this the right place to address this issue, or am I missing something obvious?