Closed maxxkia closed 6 years ago
<ns1:landingPage>
, <ns1:scmInfo>
, connection
, developerConnection
and url
are obtained directly from Maven. I assume that Maven automatically internally extends these settings as part of the POM inheritance process.
It is something beyond our control - i.e. it is a Maven issue, not an OMTD issue. Regarding the URL, I have opened a Maven issue (https://issues.apache.org/jira/browse/MNG-6384) - however, I expect the "solution" has to be that all the elements need to be redeclared in the child modules with the same values as in the parent module to prevent this behavior.
Below I am pasting a shortened version of the metadata file that was produced for my pdf reader component.
I can spot some problems:
<ns1:landingPage>
value is not valid. Artifact name should not be appended to the url. Correct link should be either https://github.com/openminted/uc-tdm-socialsciences or https://github.com/openminted/uc-tdm-socialsciences/tree/master/ss-io-pdf<ns1:characterEncodings></ns1:characterEncodings>
is empty in<ns1:inputContentResourceInfo>
and<ns1:outputResourceInfo>
<ns1:keywords></ns1:keywords>
<ns1:scmInfo>
againconnection
,developerConnection
andurl
are appended with module name (ss-io-pdf) which is incorrect.