AEM 6.1 java 1.8 compatibility issue | Community
Skip to main content
lakshmi_raghava
New Participant
October 16, 2015
Solved

AEM 6.1 java 1.8 compatibility issue

  • October 16, 2015
  • 14 replies
  • 7185 views

Hi,

we are trying to upgrade our project to AEM 6.1 and JDK 1.8 version . 

 

we are trying to modify the pom.xml files of my project. 

we used  the following combinations :

 

<plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-compiler-plugin</artifactId>
                    <version>3.1</version>
                    <configuration>
                    <source>1.8</source>
                    <target>1.8</target>
                </configuration>
                </plugin>

<plugin>
                    <groupId>org.apache.felix</groupId>
                    <artifactId>maven-scr-plugin</artifactId>
                    <version>1.21.0</version>
                    <extensions>true</extensions>
                     <configuration>
                    <sourceExcludes>com/sapient/archive/*.java</sourceExcludes>
                </configuration>               
                    <executions>
                        <execution>
                            <id>generate-scr-scrdescriptor</id>
                            <goals>
                                <goal>scr</goal>
                            </goals>
                            
                        </execution>
                    </executions>
                </plugin>

 

 

<dependency>
            <groupId>org.apache.felix</groupId>
            <artifactId>org.apache.felix.scr.annotations</artifactId>
            <version>1.9.6</version>
            <scope>provided</scope>
        </dependency>

 

if we use the following combination in parent and as well and child we are getting the following error: 

 

[ERROR] Failed to execute goal org.apache.felix:maven-scr-plugin:1.21.0:scr (generate-scr-scrdescriptor) on project aem.foundation: SCR Descriptor parsing had failures (see log) -> [Help 1]

 

if we use the above combination only in parent, build got the success, but generated jar file is not creating OSGI-INF folder . 

 

 

can anyone please provide the sample pom.xml file which will both compatible with 1.7 and 1.8 . 

 

 

 

Thanks, 

Lakshmi Raghava Reddy M.

 

can any one help

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 ogill

There seems to be some details on this issue online, looks like your java code may need to be updated. What version of AEM are you migrating from?

https://issues.apache.org/jira/browse/FELIX-4586

http://apache-sling.73963.n3.nabble.com/jira-Created-SLING-3792-Fields-in-ResourceAccessSecurityTracker-must-be-declared-volatile-td4036780.html

14 replies

lakshmi_raghava
New Participant
October 16, 2015

Hi Opkar,

Yes there are some errors, it's related my project. But with out having project code deployment, following out of box components are in unsatisfied  mode. I am using Java 8 in my local.

 

com.adobe.acs.commons.forms.helpers.impl.ForwardAsGetFormHelperImpl    unsatisfied (reference)    
 
2278     com.adobe.acs.commons.forms.helpers.impl.PostRedirectGetFormHelperImpl    unsatisfied (reference)    
 
2313     com.adobe.acs.commons.forms.impl.FormsPostFilterImpl    unsatisfied (reference)    
 
2315     com.adobe.acs.commons.forms.impl.FormsPostRedirectGetFilterImpl    unsatisfied (reference)    
 
2304     com.adobe.acs.commons.quickly.impl.QuicklyFilter    unsatisfied (reference)    
 
2316     com.adobe.acs.commons.quickly.impl.QuicklyInitServlet    unsatisfied (reference)    
 
2266     com.adobe.acs.commons.quickly.impl.QuicklyServlet    unsatisfied (reference)    
 
1305     com.adobe.cq.dam.mac.sync.helper.impl.MACSyncClientImpl    unsatisfied (reference)    
  
272     com.adobe.granite.httpcache.impl.ExpiresCacheHandler    unsatisfied (reference)    
 
1108     com.day.cq.workflow.impl.email.EMailNotificationService    unsatisfied (reference)    
  
1101     com.day.cq.workflow.impl.email.TaskEMailNotificationService    unsatisfied (reference)    
  
200     org.apache.sling.resourceaccesssecurity.impl.ApplicationResourceAccessSecurityImpl    unsatisfied (reference)    
----------------------------------------------------

Please let me know, whether we can ignore those issues or not? 

 

 

 

Thanks,

Lakshmi Raghava Reddy M.

New Participant
October 16, 2015

Hi, I am also facing the similar kind of problem. Please let me know if there is any fix

lakshmi_raghava
New Participant
October 16, 2015

Yes, we figure out the issue and issue and issue is with the code that we modified for the deprecated API. With out code changes of Deprecated API, everything is working fine with java 8 .

joerghoh
Employee
October 16, 2015

Unsatiesfied components are not an issue in the first place. A number of them will only get active if you provide proper configuration. This depends on the component.

Kind regards,
Jörg