Uploaded image for project: 'Build'
  1. Build
  2. BUILD-32

Helper Shell Scripts for modules error out on checkout and update of blossom

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • None
    • None
    • None

      When using the checkout.sh and all.sh shell scripts, an error occurs when it tries to checkout or update blossom. I believe this is caused by the directory structure of the blossom module within subversion, it is different from that of the other modules.

      Currently the directory structure is:

       
      + modules
          + blossom
              + magnolia-module-blossom
                  + branches
                  + tags
                  + trunk
      

      I believe it should be either of the approaches below:

      Approach 1

       
      + modules
          + magnolia-module-blossom
              + branches
              + tags
              + trunk
      

      Approach 2

      If the intent is to have submodules under blossom, similar to the directory structure of the standard-templating-kit, it would be:

       
      + modules
          + blossom
              + branches
              + tags
              + trunk
                  + magnolia-module-blossom
      

      In either event, the shell scripts expect the trunk directory to be directly after the module.

      svn checkout http://svn.magnolia-cms.com/svn/community/modules/blossom/trunk blossom
      

      If approach 1 is taken, the scripts would need to be updated to reference magnolia-module-blossom instead of blossom if the second approach is taken, the shell scripts can remain the same. Either approach will require modifying the directory structure of the blossom module within the subversion repository.

      Please let me know if you have any questions.

      Thanks,
      Matt

        Acceptance criteria

              gjoseph Magnolia International
              mderting Matt Dertinger
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: