-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2163 breakout mirador #75
Conversation
Mirador must be built locally with plugins included.
That is a weird one, it's like phpcpd is looking in the wrong place. |
Looks like this is a known open issue with PHPCPD v. 6.0.3 Since this issue is open we could perhaps pin phpcpd to v. 6.0.2 |
I've found the issue, it's in how phpcpd is invoked in islandora_ci: phpcpd is invoked via this command travis_scripts.sh:phpcpd --suffix *.module,*.inc,*.test,*.php $GITHUB_WORKSPACE/build_dir From the phpcpd command help text --suffix <suffix> Include files with names ending in <suffix> in the analysis
(default: .php; can be given multiple times) "Can be given multiple times" tells me that you can't actually have multiple extensions separated by a comma as above. It looks like the way the program parses the command-line argument makes it only use the last one, in this case *.php. Islandora Mirador is the only module currently part of Islandora Defaults that has an actual .php file inside it, so removing it causes the job to display the "no files found" message. vagrant@islandora8:/var/www/html/drupal/web/modules/contrib/islandora_defaults$ git checkout 2163-breakout-mirador
Switched to branch '2163-breakout-mirador'
vagrant@islandora8:/var/www/html/drupal/web/modules/contrib/islandora_defaults$ phpcpd --suffix *.php .
phpcpd 6.0.3 by Sebastian Bergmann.
No files found to scan
vagrant@islandora8:/var/www/html/drupal/web/modules/contrib/islandora_defaults$ echo $?
1 This error happens with all 6.0.x versions of phpcpd. But if we invoke it correctly no error is shown: vagrant@islandora8:/var/www/html/drupal/web/modules/contrib/islandora_defaults$ phpcpd --suffix *.php --suffix *.module --suffix *.inc --suffix *.install --suffix *.test .
phpcpd 6.0.3 by Sebastian Bergmann.
No clones found.
Time: 00:00.008, Memory: 4.00 MB
vagrant@islandora8 I know more than I care to about this utility now. I'll make a PR for islandora_ci. |
Marked as draft until Islandora/islandora_ci#16 is merged so I can continue testing the new CI failure. |
This prevents the situation where a module is sitll enabled but has been deleted from the code base.
Once @inikolaidis adds islandora/islandora_mirador to Packagist this can be taken out of draft and tested / merged. It now requires islandora_mirador in composer so a site is not left with an enabled module that has been deleted from the code base. |
Taking this out of draft since islandora_mirador has been put up on Packagist. |
Re-ran failing tests, the failure seemed to be in composer not finding the islandora/island package. No error on most recent run.ora_mirador |
This reverts commit b7030b6. Put CI back to normal.
Should we consider this a major version bump? Then, the ... otherwise, yeah, seems to do the trick:
|
Making it 3.x makes sense to me, Islandora Defaults the twilight era. |
GitHub Issue: (link)
Islandora/documentation#2163
Mirador module to be moved to Islandora organization: https://github.com/alxp/islandora_mirador
What does this Pull Request do?
Remove islandora_mirador so it can be a standalone module.
What's new?
Islandora Mirador will be moved to a separate module.
(i.e. Regeneration activity, etc.)? No
How should this be tested?
When a PR to introduce the islandora_mirador module to Islandora is created, installing that module should, via a composer conflict config, trigger this module to be updated.
Then Clear cache, restart your web server, and interact with Mirador as you normally would�..
Additional Notes:
Any additional information that you think would be helpful when reviewing this
PR.
You can't as far as I know declare that a module is incompatible with a range of commits on e.g. a dev branch so if your installation relies on a dev branch of islandora_defaults the conflict will not appear.
Updating the module versions in composer should still pull down compatible versions however, once this PR is merged and a point release is made.
Interested parties
Tag (@ mention) interested parties or, if unsure, @Islandora/8-x-committers