Konrad Windszus

Superseded by #765.

This is known, reported and fixed in https://issues.apache.org/jira/browse/SLING-9117. There is just not yet a new Eclipse Sling IDE release containing the fix.

The problem is the local or non Cloud environments, because compiling against a newer AEM API changes the compatible version ranges, i.e. in general the generated bundles do no longer...

To clarify: The problem is the standard import version range being generated by Bnd (https://bnd.bndtools.org/chapters/170-versioning.html#import-version-policy)

Here is a pom.xml snippet which allows it to run ``` ... org.apache.maven.plugins maven-dependency-plugin 3.1.2 download-validator package unpack somegroupid someartifactid zip 2.0.23 org.codehaus.mojo exec-maven-plugin 3.0.0 run-validator exec verify ${project.build.directory}/dependency/validator ${project.build.directory}...

In fact the version of the plugin is only defined if the archetype is used with the cloud options (https://github.com/adobe/aem-project-archetype/blob/21dea7234123d60e1803cd707c3b6ef977ff581e/src/main/archetype/pom.xml#L95) but the module is included even when being included in...

This duplicates #685

> Use of writeRaw() however should be supported for such case. Unfortunately not. If I call the following methods, I get the exception from above ``` writeStartTag(...) writeRaw(...) writeAttribute(...) ```...

> writeRaw() I think should not modify the state This is tricky from a backwards-compatibility point of view as the API javadoc explicity says > It will not update state...

The Sling Sightly Compiler seems to understand all formats of attribute values: https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler/blob/01a7b922d5c2f89974534cdeba0c8373d92a24c1/src/main/java/org/apache/sling/scripting/sightly/impl/html/dom/TagTokenizer.java#L203