docs: multi-line import example for page directive

[scscgit]

Documentation didn't cover the case of multiple page imports, which requires semicolons ;. Newbies could try separating them by spaces, which would cause an error Unexpected input: 'com'.

Additionally, I'd like to take this opportunity to ask you to introduce a guideline for optimal code quality. For projects with large number of imports, e.g. when you pass many objects to GSP to work with them, it's beneficial to avoid import being an insanely long line. For version control, you also want to reduce conflicts and individually see git blame for each import. However, to separate lines, you must add an undocumented workaround of a trailing backslash \, otherwise you get an error Unexpected input: '\n'.

Additional questions also arise when you're about to establish a baseline for a new project, which is why I ask you to define a convention here that you expect projects to follow by default, as a de-facto standard. For example:

1. First import could start on a new line:

import="\
java.awt.*; \

2. There can be a trailing ; after the last import to reduce diff.

• However, if we end with ; \ and put " %> at the next line, there is an error Unexpected input: '\r\n'.
• But if we end the last import without ;, only with \, then it's possible to put " %> as the last line. In this case we can't avoid frequent changes when new imports are added.

3. We could skip the space before \...

🗒️ The errors are reported under org.codehaus.groovy.control.MultipleCompilationErrorsException: org.grails.gsp.GroovyPagesException: Could not parse script: startup failed.

[CLAassistant]

All committers have signed the CLA.