david g.
@Lovepreet1994 did you log the same issue twice? #439 and #440 using 2 different user names? Are these duplicates? If so can you close so we can focus on 1...
@justinedelson If i picked No id still want (an option) to create the base WF sling:OsgiConfig node even if it was empty (just the pid and empty prop pairs) IMO...
@shajiahmed hi - which guide is this about? Can you provide some more details? thanks
@shajiahmed bump - can you provide info where this missing?
Experiencing the same. Did we skip 38 and go straight to 39? https://search.maven.org/artifact/com.adobe.aem/aem-project-archetype Thought, 39 also fails ... ``` tmp mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \ -D archetypeGroupId=com.adobe.aem \ -D archetypeArtifactId=aem-project-archetype \...
+1 .. it should work in 5.x -- though well probably remove it in 6.0.0
@gcalandria this looks right. You of course have to goto CM Configuration the "development environment" and set the `ENVIRONMENT_NAME` to `DEV` and then the same for the the QA environment's...
@joerghoh @kwin im all on board with 6.5.x+ for AEM 6.0.0 ... i wouldnt even be adverse to specifying a higher level SP if it provides us more flexibility. One...
I think we need to do more work on Dispatcher Flush UI where we can include this.
@raducotescu 1. How would we distinguish between AEM SDK dev and AEM as a Cloud service dev? Would a OSGi config on AEM as a Cloud Service Dev be problematic?...