Konrad Windszus
Konrad Windszus
Tracecompass has also maintained some external annotations for quite some libraries in the past. It seems right now much more extensive than this approach. Could you just merge all changes...
Currently for mapping LDAP entries to ODM annotated classes the `objectclass` field on the annotation `@Entry` is evaluated. The mapping considers only LDAP entries having the given class explicitly set...
Even with ODM there is no built-in conversion from the String representation of date values from LDAP to native Date types (see #167). Please support a conversion from `String` to...
When executing the first step from https://github.com/adobe/aem-test-samples/blob/aem-cloud/ui-selenium-webdriver/README.md#all-in-one with Maven 3.9.6 you run into the following error: `[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install) on project com.adobe.cq.cloud.testing.ui.java.ui.tests: The packaging plugin for...
https://github.com/adobe/aem-testing-clients/wiki/Best-practices#junit-rules should be accompanied with according extensions for JUnit 5 (https://junit.org/junit5/docs/current/user-guide/#extensions)
Currently there seems to be no way to change the response headers for theme resources (https://github.com/adobe/aem-site-template-standard/tree/main/theme). Please allow to at least configure the most basic ones as `Cache-Control` and `Content-Type`.
Currently the readme only states: > Required dependencies: node, npm, mvn Please give a hint on the supported versions (minimum and also maximum if applicable).
With `aemanalyser:1.5.8:project-analyse` I get the following exception ``` [INFO] --- aemanalyser:1.5.8:project-analyse (analyser) @ novonordisk-aem-hcp-integrations-all-container --- Downloading from central: https://repo.maven.apache.org/maven2/com/adobe/aem/aemanalyser-maven-plugin/maven-metadata.xml Downloaded from central: https://repo.maven.apache.org/maven2/com/adobe/aem/aemanalyser-maven-plugin/maven-metadata.xml (1.6 kB at 15 kB/s) Downloading from...
Currently each container package is analysed separately which means that dependencies from one container content package to another is not correctly reflected in the analysis as the plugin incorrectly assumes...
A link to https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/developing/archetype/build-analyzer-maven-plugin would be helpful to have in the README for the maven plugin (https://github.com/adobe/aemanalyser-maven-plugin/blob/main/aemanalyser-maven-plugin/README.md)