[
http://jira.magnolia-cms.com/browse/BUILD-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Dertinger updated BUILD-32:
--------------------------------
Description:
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:
{noformat}
+ modules
+ blossom
+ magnolia-module-blossom
+ branches
+ tags
+ trunk
{noformat}
I believe it should be either of the approaches below:
h2. Approach 1
{noformat}
+ modules
+ magnolia-module-blossom
+ branches
+ tags
+ trunk
{noformat}
h2. Approach 2
If the intent is to have submodules under blossom, similar to the directory
structure of the standard-templating-kit, it would be:
{noformat}
+ modules
+ blossom
+ branches
+ tags
+ trunk
+ magnolia-module-blossom
{noformat}
In either event, the shell scripts expect the trunk directory to be directly
after the module.
{code}
svn checkout http://svn.magnolia-cms.com/svn/community/modules/blossom/trunk
blossom
{code}
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
was:
When using the checkout.sh and all.sh shell scripts, and 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:
{noformat}
+ modules
+ blossom
+ magnolia-module-blossom
+ branches
+ tags
+ trunk
{noformat}
I believe it should be either of the approaches below:
h2. Approach 1
{noformat}
+ modules
+ magnolia-module-blossom
+ branches
+ tags
+ trunk
{noformat}
h2. Approach 2
If the intent is to have submodules under blossom, similar to the directory
structure of the standard-templating-kit, it would be:
{noformat}
+ modules
+ blossom
+ branches
+ tags
+ trunk
+ magnolia-module-blossom
{noformat}
In either event, the shell scripts expect the trunk directory to be directly
after the module.
{code}
svn checkout http://svn.magnolia-cms.com/svn/community/modules/blossom/trunk
blossom
{code}
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
> Helper Shell Scripts for modules error out on checkout and update of blossom
> ----------------------------------------------------------------------------
>
> Key: BUILD-32
> URL: http://jira.magnolia-cms.com/browse/BUILD-32
> Project: Build
> Issue Type: Bug
> Reporter: Matt Dertinger
> Assignee: Grégory Joseph
>
> 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:
> {noformat}
> + modules
> + blossom
> + magnolia-module-blossom
> + branches
> + tags
> + trunk
> {noformat}
> I believe it should be either of the approaches below:
> h2. Approach 1
> {noformat}
> + modules
> + magnolia-module-blossom
> + branches
> + tags
> + trunk
> {noformat}
> h2. Approach 2
> If the intent is to have submodules under blossom, similar to the directory
> structure of the standard-templating-kit, it would be:
> {noformat}
> + modules
> + blossom
> + branches
> + tags
> + trunk
> + magnolia-module-blossom
> {noformat}
> In either event, the shell scripts expect the trunk directory to be directly
> after the module.
> {code}
> svn checkout http://svn.magnolia-cms.com/svn/community/modules/blossom/trunk
> blossom
> {code}
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
