Level 2

Solved

Upgrade AEM 6.0 SP1 to Java8

6 replies
2311 views
Translate

Am trying to upgrade AEM 6.0 with SP1 to Java8 and having problems with it. Wondering if anyone have upgraded to Java8 on AEM 6.0 SP1.

One of my bundle is not started and am seeing the below issues on the bundle.

com.sun.javadoc -- Cannot be resolved but is not required and overwritten by Boot Delegation

com.sun.msv.datatype -- Cannot be resolved but is not required and overwritten by Boot Delegation

com.sun.msv.datatype.xsd -- Cannot be resolved but is not required and overwritten by Boot Delegation

com.sun.tools.javadoc -- Cannot be resolved but is not required and overwritten by Boot Delegation

hidden.org.codehaus.plexus.interpolation -- Cannot be resolved but is not required

junit.framework -- Cannot be resolved but is not required

junit.textui -- Cannot be resolved but is not required

net.sf.cglib.proxy -- Cannot be resolved but is not required

nu.xom -- Cannot be resolved but is not required

org.apache.crimson.jaxp -- Cannot be resolved but is not required

org.apache.tools.ant -- Cannot be resolved but is not required

org.apache.tools.ant.taskdefs -- Cannot be resolved but is not required

org.apache.tools.ant.types -- Cannot be resolved but is not required

org.apache.xml.resolver -- Cannot be resolved but is not required

org.apache.xml.resolver.tools -- Cannot be resolved but is not required

org.codehaus.plexus.interpolation -- Cannot be resolved but is not required

org.gjt.xpp -- Cannot be resolved but is not required

org.hibernate.cache -- Cannot be resolved but is not required

org.jaxen -- Cannot be resolved but is not required

org.jaxen.dom4j -- Cannot be resolved but is not required

org.jaxen.pattern -- Cannot be resolved but is not required

org.jaxen.saxpath -- Cannot be resolved but is not required

org.jdom -- Cannot be resolved but is not required

org.jdom.input -- Cannot be resolved but is not required

org.joda.time,version=[2.9,3) -- Cannot be resolved but is not required

org.joda.time.format,version=[2.9,3) -- Cannot be resolved but is not required

org.openxmlformats.schemas.officeDocument.x2006.math -- Cannot be resolved but is not required

org.openxmlformats.schemas.schemaLibrary.x2006.main -- Cannot be resolved but is not required

org.relaxng.datatype -- Cannot be resolved but is not required

org.springframework.util,version=[3.1,4) -- Cannot be resolved but is not required

org.xmlpull.mxp1 -- Cannot be resolved but is not required

org.xmlpull.v1 -- Cannot be resolved but is not required

schemasMicrosoftComOfficePowerpoint -- Cannot be resolved but is not required

schemasMicrosoftComOfficeWord -- Cannot be resolved but is not required

spiffy.core.util -- Cannot be resolved but is not required

sun.misc -- Cannot be resolved but is not required and overwritten by Boot Delegation

sun.reflect -- Cannot be resolved but is not required and overwritten by Boot Delegation

Below are some of maven version

<maven-bundle-plugin.version>3.0.1</maven-bundle-plugin.version>

<maven-scr-plugin.version>1.20.0</maven-scr-plugin.version>

<maven-sling-plugin.version>2.1.0</maven-sling-plugin.version>

<jibx-run.version>1.3.1</jibx-run.version>

<org.apache.felix.scr.annotations.version>1.9.6</org.apache.felix.scr.annotations.version>

<maven-surefire-plugin.version>2.20.1</maven-surefire-plugin.version>

<guava.version>14.0.1</guava.version>

Any help/pointers is much appreciated!

Thanks

Basheer

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Basheer_PinjariAccepted solution

Level 2

Thanks all who looked into this and helped me with tips. Below is what I figured out with Adobe

Seems like Java 8 is officially supported but with special installation. Installing SP1 via package manager is not sufficient to include Java 8 support.

Perform the following steps to install an initial AEM 6.0 instance with the Service Pack. This method is required to install AEM with a Java 8 VM:

1. Login to Package Share and download the Service Pack 1 ZIP to your local file system

2. Unpack the Quickstart using the java -jar *.jar -unpack command.

3. Create the install directory in crx-quickstart.

4. Copy the Service Pack package in the install folder.

5. Start the Quickstart.

smacdonald2008

Level 10

I am happy to hear you got it working.

Translate

Basheer_PinjariAuthorAccepted solution

Level 2

Thanks all who looked into this and helped me with tips. Below is what I figured out with Adobe

Seems like Java 8 is officially supported but with special installation. Installing SP1 via package manager is not sufficient to include Java 8 support.

Perform the following steps to install an initial AEM 6.0 instance with the Service Pack. This method is required to install AEM with a Java 8 VM:

1. Login to Package Share and download the Service Pack 1 ZIP to your local file system

2. Unpack the Quickstart using the java -jar *.jar -unpack command.

3. Create the install directory in crx-quickstart.

4. Copy the Service Pack package in the install folder.

5. Start the Quickstart.

Translate

smacdonald2008

Level 10

The AEm 6 version just started using JDK 8. It supports it much better in later versions. For that version, I used JDK 7 for much better stability.

Translate

Basheer_PinjariAuthor

Level 2

Yes, if I change JDK to 7 it works. But the strange thing is AEM 6.0 with SP1 and Java 8 worked fine in our mac OS local machines.

Translate

smacdonald2008

Level 10

Back in AEM 6 - not even sure Java 8 was supported. Checking docs. Those missing libs are part of AEM - therefore no need to add them. If you change your JDK to 7 - it works right?

Also - AEM 6.0 is very old and not supported by Adobe anymore- Most of the community is on a much newer AEM version.

Translate

kautuk_sahni

Employee

Seems like versions problem.

You can always check if a package exists in AEM by using the AEM dependency finder: http://localhost:4502/system/console/depfinder

Also refer to this answer:- Re: Maven Dependencies

// This means that these packages are not in the AEM OSGi service container. These missing packages need to be included into AEM.

Place the JAR(s) that contain these packages into an OSGi bundle and deploy to AEM.

another reference post to read:-

Translate

Kautuk Sahni

Sign up

Login with SSO

Login to the community

Login with SSO