I have tried installing a users and user groups package created from 5.6.1 onto AEM 6.2 with below filter definition. While installing, it threw org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0027: The admin user cannot be remove...

Thanks Kautuk

Thanks Opkar for your input. In the case of incremental upgrade, how could we identify the recent changes. Is it by using http://adobe-consulting-services.github.io/acs-aem-commons/features/query-packager.html

It might not be what you need. It is possible to display the map as a static image on the page. https://developers.google.com/maps/documentation/static-maps/

We have many sites running on 5.6.1 and we successfully did the in-place upgrade. As each site takes time to test, we would like to deploy it site by site on production by switching DNS to point to the new 6.2 site once thoroughly tested.Can we create packages from 5.6.1 and deploy it in the new ins...

I have not faced any issue with using 1.6. Currently I have JDK 1.8 installed and I am just curious to know if we should not change this from 1.6 in the POM for a upgrade activity from 5.6.1 to AEM 6.2.  I've tried using 1.8 which resulted in rewriting the classes using obsolete APIs like java.util....

As per the  the recommended Java version for AEM 6.2 is Java 8. I was just looking at the POM used in we.retail reference github page as this package is intended for AEM 6.2. https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail/blob/master/pom.xml.Here I could see that maven compiler plugin...

Thank you all for the support. 

Hi I have successfully tested consuming a soap web service by following the helpx website. https://helpx.adobe.com/experience-manager/using/creating-cxf-bundles-consume-web.html. Here the webservices are open to publicWe have a requirement to implement the same approach using SOAP webservices. This ...

Thanks for the update Lokesh. We will make this change eventually.However, as quick work around, just thought of asking if it is really possible to reintroduce this nodetype in AEM 6.1 by installing a package or something.