The dependency of an AEM project fails when a developer configures using Apache Maven. Refer to the error information below.
INFO] ---------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] ---------------------------------------
[ERROR] /training/core/src/main/java/com/adobe/training/core/listeners/SimpleResourceListener.java:[18,28] package org.apache.sling.api does not exist
[ERROR] /training/core/src/main/java/com/adobe/training/core/filters/LoggingFilter.java:[26,28] package org.apache.sling.api does not exist
[ERROR] /training/core/src/main/java/com/adobe/training/core/filters/LoggingFilter.java:[27,31] package org.apache.sling.engine does not exist
[ERROR] /training/core/src/main/java/com/adobe/training/core/models/HelloWorldModel.java:[22,37] package org.apache.sling.api.resource does not exist
[ERROR] /training/core/src/main/java/com/adobe/training/core/models/HelloWorldModel.java:[25,33] package org.apache.sling.api.settings does not exist
[ERROR] /training/core/src/main/java/com/adobe/training/core/models/HelloWorldModel.java:[31,13] cannot find symbol symbol: class SlingSettingsService location: class com.adobe.training.core.models.HelloWorldModel What should a developer add to the pom.xml to fix the Maven build?
A developer needs to configure sets of values according to the following parameters:
- Varies for different staging environments
- Varies for different content paths
- Diffets between author and publish
Which implementation strategy should the developer use to meet these requirements?
A custom AEM application has a run time dependency to a third party OSGi bundle that is NOT included in out-of-the-box AEM. The third party dependency needs to be available for multiple applications and be upgraded separately from the custom AEM application.
How should a developer make sure that the bundle is installed on all environments?
A developer needs to create a new component called "Component A". Component A must show a list of other components that all have a resource type of existing "Component B". Component A must render this list of tiles for each Component B where the tile rendering is different from the default one. The list of rendered tiles must be reusable by future new components.
How should the developer implement this functionality?
A developer wants to change the log level for a custom API.
Which OSGi configuration should the developer modify?