I'm going to post this here in case people find this thread before they find mine.This issue is caused by the obfuscator that has been run on the AEM 6.1 uber-jar.  That obfuscator removes methods that the Java 1.8 bytecode verifier needs to be there. If you request the unobfuscated jar from support...

So, I have installed AEM 6.1 many times with nosamplecontent, and never encountered this issue.  So, if it was implemented in AEM 6.1, it was not in the same way.I will try the geometrixx super package removal - in the past it was impossible to completely remove them once they were installed.I would...

Thanks, Scott!Yes, ticket number is 90121, they referred me to to this page: https://docs.adobe.com/docs/en/aem/6-2/administer/security/production-ready.html

It appears from a support ticket that I opened, that in AEM 6.2 installing a server with the runmode of 'nosamplecontent' also forces the 'productionready' stuff, including disabling crx/de.If I'm understanding this correctly, there is now no way to build out a development environment without all th...

This appears to be an issue with the AEM 6.1 Obfuscated Uber Jar.  The obfuscator appears to have removed various bits and pieces from the bytecode that the Java 1.8 compiler is requiring to be there.I got the unobfuscated Uber Jar from AEM support, and after much Maven wrangling, was able to compil...

Yes, it compiles just fine under 1.7:[INFO] --- maven-sling-plugin:2.1.0:install (install-bundle) @ ewcm.global.core --- [INFO] Installing Bundle ewcm.global.core(C:\Projects\EWCM_Projects\ewcm\core\target\ewcm.global.core-1.0.51-SNAPSHOT.jar) to http://localhost:4502/crx/repository/crx.default/apps...

Hello -  Using Java 1.8u77, and the uber-jar 6.1.0-SP1, when trying to compile, I am seeing this error which is preventing the code from compiling.at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecut...

So, I already had defined the Adobe repo profile in my pom.xml, just like in the Archetype.However, despite being set to be active by default in the POM, it wasn't kicking in every time the build ran for some reason.If I run:mvn help:active-profilesit kicks in every time, but onclean installit does ...

Thanks all, the settings.xml did the trick.  I really appreciate the responses!This is going to be a huge mess to get a settings.xml on to all our build servers, developer laptops so forth on computers all over the world, since it doesn't go into source code control in a repeatably-installable place...

Trying to do a fresh build on a new computer:[INFO] Downloading: https://repo.maven.apache.org/maven2/com/day/jcr/vault/content-package-maven-plugin/0.0.24/content-package-maven-plugin-0.0.24.pom[WARNING] The POM for com.day.jcr.vault:content-package-maven-plugin:jar:0.0.24 is missing, no dependency...