cancel
Showing results for 
Search instead for 
Did you mean: 

error with creation of mtar archive

former_member506840
Discoverer
0 Kudos

we are using the Cloud MTA Build Tool for building our maven based project and create a mtar

we have our mtad.yaml defined as below ,where the war file is generated by the assembly project as war which needs to be just archived as mtar .

from the exising project war creation is fine , but while creating a mtar we are seeing the below error

error

path does not exist; the content type was not defined

_schema-version: "3.1"
ID: com.sap.api.cf.module
version: 1.0.0
modules:
- name: modulename
  type: java.tomee
  path: modulename/target/modulename.war
former_member506840
Discoverer
0 Kudos

if i specify the path: modulename as this value it creates a mtar with whole directory of module including the src

Accepted Solutions (0)

Answers (1)

Answers (1)

Ivan-Mirisola
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Sandeep Manjunath,

I don't think you have to specify the war file on an mtar yaml file. It is different than a manifest file.

The file extension is not configurable; it is predefined by the module type (.zip or .war).

https://help.sap.com/viewer/58746c584026430a890170ac4d87d03b/Cloud/en-US/b55e2d06ca7048f087d09ad4373...

The module's type is the way the mtar builder knows how to build that module and what to look for in terms of deployable artifact.

path is just the means to point a module to a directory where it should find that module. Name is just a name, you could choose whatever is easier to read and reference modules across the yaml.

Best regards,
Ivan