Correct. When you kick off the workflow through the Project UI the project.path is set on the workflow's metadata node.Possible workarounds when using the workflow launcher is to persist a project path property via workflow process step prior to  the Create Task step.

I'd look into using Sling Mocks or other mocking frameworks to simulate complex objects that are impractical to incorporate into the unit test. The goal should be to isolate and test behavior of the code within the servlet, not necessarily the servlet itself. Check out Sling Mocks: Apache Sling :: S...

In some cases, due to the AEM sites editor rendering the page in an iframe, certain CSS/JS is not compatible. It seems that you are running into that when using vh units. The work around is to have a small amount of CSS that is only loaded on the Authoring environment (wcmmode=edit / preview). This ...

Ultimately the method getCssClassNames() of ComponentContext is called: aem-core-wcm-components/PageImpl.java at master · Adobe-Marketing-Cloud/aem-core-wcm-components · GitHub .This is an internal api, but has some logic built in to inspect the component and add classes based on the name of the com...

In AEM 6.4 managing Closed User Groups for Assets is available ootb. A video can be found here: Using Closed User Groups with AEM Assets Unfortunately I don't know if this feature will be back ported to AEM 6.3...

Another user had a similar issue and it was because the version of Java was not 1.8. More details here: Unresolved dependencies on fresh AEM 6.3.1 · Issue #12 · Adobe-Marketing-Cloud/aem-guides-wknd · GitHub

The error indicates that Core Components Page model is not registered correctly. A couple of things to check:1. Verify Local AEM Instance setup:Java 1.8AEM 6.3Service Pack 1​6.3 Feature Pack 205932. Verify that Core Components 2.0 have been uploaded and installed by navigating to CRX Pack Manager (h...

Hi Madiha,IIRC a common convention in CQ development pre 6.x was to name the maven module content -> for htl, jsp, CSS/JS, etc... and bundle for OSGi/Java code. Since we now refer to content as page content it was confusing. The new convention is ui.apps -> for htl, CSS/JS, configs and core for OSGi...

Thanks alexr2​!

alexr2​ to clarify, did updating those dependencies in WKND pom.xml fix the issue? Or were you experiencing this issue in your own project and updating those dependencies fixed it? You mention "the archetype has a lot outdated references" is that when creating a project using Lazybones or the using ...