AEM 6.2 and Java 8 maven project POM | Community
Skip to main content
A
aemanonymous
July 13, 2016
Solved

AEM 6.2 and Java 8 maven project POM

  • July 13, 2016
  • 3 replies
  • 1868 views

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 uses Java Source and Target as 1.6. Could anyone please let me know if the sources for AEM 6.2 has to be compiled against 1.8.

 

                                    
<plugin>
 <groupId>org.apache.maven.plugins</groupId>
 <artifactId>maven-compiler-plugin</artifactId>
 <configuration>
 <source>1.8</source>
 <target>1.8</target>
 <encoding>UTF-8</encoding>
 </configuration>
 </plugin>

 

Also it would be really great to understand which are the recommended versions to be used for compiler plugin, scr annotations plugin etc.in AEM 6.2 project POM. Any pointers or thoughts would be really appreciated.

 

Best regards

Paul

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

    We did update it to 1.8. Though on updating it to 1.8 you would need to make couple updates to the classes which would be really minor, one such that you pointed out. 

    Now although the version 1.7 works well for me, you will want to update it per the specs(by Adobe) for the version of AEM you plan on using.

    3 replies

    GK-007
    GK-007
    July 13, 2016

    For AEM 6.2 i am using 1.6 as source and target not seeing any issue.

    Do you see  any issue from your end??

    Thanks,

    Kishore

    A
    aemanonymousAuthor
    July 13, 2016

    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.Dictionary. My gut feeling was to leave it to 1.6/1.7 because that is what is being used in almost all the sample projects which I have seen, but just wanted to get an expert opinion in this topic.

    N
    NitroHazeDevAccepted solution
    Level 9
    July 13, 2016

    We did update it to 1.8. Though on updating it to 1.8 you would need to make couple updates to the classes which would be really minor, one such that you pointed out. 

    Now although the version 1.7 works well for me, you will want to update it per the specs(by Adobe) for the version of AEM you plan on using.

      Terms & ConditionsAccessibility statement

      Loading footer...