1
0
-1

Hi, we are looking for an example of a .library-config.xml so we can successfully import a custom component in relation to https://support.avoka.com/confluence/display/ATMA/.Creating+Maestro+Native+Components+v5.0


Can you provide a template for this ? Thanks

    CommentAdd your comment...

    2 answers

    1.  
      2
      1
      0

      Hi Garry,

      You can download the whole toolkit, which includes a library config XML file template.  The link is at 

      If you just want one that has already been populated, you could use this:

      <?xml version="1.0" encoding="UTF-8"?>
      <Library sfmVersion="5.0.0" revisionNumber="1" exportDate="2017-07-06" environmentName="Custom Development Environment">
      <description>Custom Components</description>
      <createdAt type="Date">1499383745632</createdAt>
      <createdBy>user@organization.com</createdBy>
      <lastModifiedAt type="Date">1499383745632</lastModifiedAt>
      <lastModifiedBy>user@organization.com</lastModifiedBy>
      <releaseMinVersion></releaseMinVersion>
      <releaseMaxVersion></releaseMaxVersion>
      <tmMinVersion></tmMinVersion>
      <readOnlyFlag>false</readOnlyFlag>
      <name>custom.components</name>
      <type>Organization</type>
      </Library>


      1. Garry Jackson

        Thanks for this but what we need to see is an example ZIP of a working component that will be accepted into Maestro using 'Import Component'. Then we can extract and work backwards and work out why Maestro is giving us this message.... no clue as to why


        See GarrysComponent.zip


        I've used zip command line and excluded files so it should meet the structure


        zip -r GarrysComponent.zip . -x "*.DS_Store" -x "*.project"


        I'm not using npm, node, gulp etc, far too many dependencies and path constraints, I would rather ZIP up as above.


        Screen Shot 2017-07-11 at 12.25.00 1.pngGarrysComponent.zip

      CommentAdd your comment...
    2.  
      2
      1
      0

      Here is a simple example of the XML configuration file:

      <?xml version="1.0" encoding="UTF-8"?>
      <Library>
         <description>Description of the library contents</description>
         <name>My library name</name>
      </Library>

        CommentAdd your comment...