8000 Improve ERROR logging on malformed RepoInit scripts · Issue #26 · adobe/aemanalyser-maven-plugin · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Improve ERROR logging on malformed RepoInit scripts #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.

Sign up for GitHub

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

Jump to bottom
Open
davidjgonzalez opened this issue Mar 9, 2021 · 0 comments
Open

Improve ERROR logging on malformed RepoInit scripts #26

davidjgonzalez opened this issue Mar 9, 2021 · 0 comments

Comments

@davidjgonzalez
Copy link

Expected Behaviour

Being able to easily troubleshoot issues reported by AEM Analyzer.

Ideally the src file (full src path), src line and line fragment would be displayed.

If too hard, path to compiled JSON in target folder, with actual file line # is reported (current line number is the line number IN the repoInit JSON Object, NOT in the .json file. To find the offending line, you need to copy ONLY the RepoInit JSON blob out of the .json file into a new file, and then look for the reported line #.

Actual Behaviour

When a RepoInit error occurrs, the error is:

{code}
[ERROR] repoinit: Parsing error in repoinit from extension : Encountered "" at line 1792, column 22.
Was expecting one of:
[ERROR] Analyser detected errors on feature 'com.adobe.aem.examples:examples.analyse:slingosgifeature:aggregated-publish.stage:1.0.0-SNAPSHOT'. See log output for error messages.
{code}

Reproduce Scenario (including but not limited to)

Create a repoinit script with the malformed rule:

{code}
create path /content/foo(Sling:Folder
{code}

Steps to Reproduce

Platform and Version

AEM analyzer version shipped with Archetype 25

Sample Code that illustrates the problem

Logs taken while reproducing problem
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@davidjgonzalez
0