non backwards compatible code -org.apache.sling.scripting.sightly | Community
Skip to main content
sivas61374651
Level 3
Jul 24, 2018 2:53 PM UTC
Solved

non backwards compatible code -org.apache.sling.scripting.sightly

Hi All,

I'm working in an 6.1 to 6.4 in-pace upgrade activity. As part of this, while I'm fixing the issues raised by pattern detector I found the below issue and I'm unable to fix this. Can any one help me to fix this? Appreciate your help

Regards,

Vijay Selvaraj

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
joerghoh
joerghohAccepted solution
Employee
Jul 26, 2018 7:45 AM UTC

When you compile the code against the 6.4 uber.jar, does the resulting bundle then resolve on AEM 6.4? If yes, everything should be fine.

jörg

View reply

9 replies

sivas61374651Author
Level 3
Jul 27, 2018 11:02 AM UTC

Thanks Much Jorg!

Translate
joerghoh
joerghohAccepted solution
Employee
Jul 26, 2018 7:45 AM UTC

When you compile the code against the 6.4 uber.jar, does the resulting bundle then resolve on AEM 6.4? If yes, everything should be fine.

jörg

Translate
sivas61374651Author
Level 3
Jul 25, 2018 9:09 AM UTC

Hi Jorg,

Below are steps I have done and tested,

1) pattern detector installed in 6.1 and ran.

2) It shows some list of defects (like deprecated sling resource type for components..and so on) and we fixed all the issue except this. Since I don't know how to fix this.

3) Ran uber jar 6.4 and ran again pattern detector - still it shows the error which i have posted here.

based on your last comment, I will not work anything on the HTL part now.  Expecting your help!

Thanks,

Vijay

Translate
joerghoh
joerghoh
Employee
Jul 25, 2018 6:33 AM UTC

You should not switch to HTL directly now (probably too much work without any benefit). But on the long run you should consider switching.

Regarding archetype version 10: When you switch to AEM 6.4, you might want to check the latest archetypes and see what plugin versions they are not using. That's not absolutely necessary, but I would recommend to keep your maven plugins up-to-date.

Jörg

Translate
joerghoh
joerghoh
Employee
Jul 25, 2018 6:25 AM UTC

Hi Vijay,

I understood that you ran the pattern detector on AEM 6.1, and that screenshot you posted originates from there. If you say now "still facing the issue", what have you done and what have you tested?

Jörg

Translate
sivas61374651Author
Level 3
Jul 25, 2018 6:24 AM UTC

Hi Donald,

Are you saying that I should rebuild the HTL components with maven archtype-13 as part of in-place upgrade to solve this issue?

Right now my application has been built for AEM 6.1 ,java version is 1.8 & maven archtype is 10.

Can you guide me somemore detail on this, if I'm wrong..

Thanks,

Vijay

Translate
sivas61374651Author
Level 3
Jul 25, 2018 6:21 AM UTC

Hi Jorg Hoh,

The code base has been built in Java 1.8 and I have already run the uber.jar for AEM 6.4. But still facing this issue alone.

Thanks,

Vijay

Translate
smacdonald2008
smacdonald2008
Level 10
Jul 24, 2018 5:36 PM UTC

When you want to use components built for an older AEM version - you have to update your components - such as HTL components - for AEM 6.4. This means rebuilding them and using the UBER 6.4 JAR file as discussed here -- Creating an Adobe Experience Manager 6.4 Project using Adobe Maven Archetype 13

Translate
joerghoh
joerghoh
Employee
Jul 24, 2018 4:17 PM UTC

The java package version has changed. Recompiling the code with the proper uber.jar should solve this issue.

Translate
Terms & ConditionsAccessibility statement

Loading footer...