Skip to content
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

Content roots scanning #274

Open
krystian-panek-vmltech opened this issue Sep 24, 2024 · 0 comments
Open

Content roots scanning #274

krystian-panek-vmltech opened this issue Sep 24, 2024 · 0 comments
Labels
improvement Improvement to an existing feature

Comments

@krystian-panek-vmltech
Copy link
Contributor

imagine running

sh aemw content pull --dir '/content/mysite/xxx'

will fail as there is no jcr_root in the local path. but... the tool could be smart and suggest the absolute path basing on scanned content roots

sh aemw content scan/roots could idempotently detect all jcr_roots in the project structure and cache it in the lock (as this usually does not change over the time)

the by using that info suggest which absolute path should be corrected

[1] /Users/krystian.panek/Projects/mysite/ui.apps/src/main/content/jcr_root/content/mysite/xxx
[2] /Users/krystian.panek/Projects/mysite/ui.content/src/main/content/jcr_root/content/mysite/xxx
[3] /Users/krystian.panek/Projects/mysite/ui.config/src/main/content/jcr_root/content/mysite/xxx

etc

@krystian-panek-vmltech krystian-panek-vmltech added the improvement Improvement to an existing feature label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

1 participant