Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Error while deploying custom AEM component

Avatar

Avatar
Validate 1
Level 2
khushbooa339108
Level 2

Likes

6 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
khushbooa339108
Level 2

Likes

6 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile
khushbooa339108
Level 2

18-12-2018

Hi,

I have built a custom AEM component 'Byline' by following AEM WKND tutorial. However, after deployment, I am not able to find my component model in AEM web console for Sling models. I am using AEM 6.4 quickstart, getting following errors while using this component:

Caused by: org.apache.sling.scripting.sightly.SightlyException: Compilation errors in org/apache/sling/scripting/sightly/apps/wknd/components/content/byline/byline_html.java:

Line 28, column 1272 : Only a type can be imported. com.adobe.aem.guides.wknd.core.components.Byline resolves to a package

Line 49, column 2354 : Byline cannot be resolved to a type

    at org.apache.sling.scripting.sightly.impl.engine.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:173) [org.apache.sling.scripting.sightly:1.0.48.1_3_1]

    ... 286 common frames omitted

Unable to resolve com.adobe.aem.guides.wknd.core [551](R 551.19): missing requirement [com.adobe.aem.guides.wknd.core [551](R 551.19)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.wcm.core.components.models)(version>=12.5.0)(!(version>=13.0.0))) Unresolved requirements: [[com.adobe.aem.guides.wknd.core [551](R 551.19)] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.wcm.core.components.models)(version>=12.5.0)(!(version>=13.0.0)))]

    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149)

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)

    at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)

    at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)

    at org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(BundleStartTask.java:97) [org.apache.sling.installer.core:3.8.12]

    at org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:902) [org.apache.sling.installer.core:3.8.12]

    at org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:737) [org.apache.sling.installer.core:3.8.12]

    at org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:287) [org.apache.sling.installer.core:3.8.12]

    at java.lang.Thread.run(Thread.java:748)

Also, I can see following error while viewing my site OSGi bundle in AEM Web console:

com.adobe.cq.wcm.core.components.models,version=[12.5,13) -- Cannot be resolved

I am not sure if I am missing any configuration or mvn dependency. Can I please get some help to resolve these errors?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
khushbooa339108
Level 2

Likes

6 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
khushbooa339108
Level 2

Likes

6 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile
khushbooa339108
Level 2

19-12-2018

Thanks for replying. It seems the tutorial was recently updated to use Core components 2.2.0 and I was using Core components 2.0.4 for models as required earlier. I have updated the configurations accordingly which has resolved all errors.

Answers (11)

Answers (11)

Avatar

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile
chrisatsirius
Level 2

03-09-2019

Yes, I was talking about pom.xml file I updated.

Avatar

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile
chrisatsirius
Level 2

30-08-2019

I am using VSCode, I experienced the same error, the parent POM already updated to core 2.4.0.

When I built with mvn, there is no error.

I wonder what else can I look at? How would I know which version of core should be used?

Thanks in advanced.

Avatar

Avatar
Validate 1
Level 2
khushbooa339108
Level 2

Likes

6 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
khushbooa339108
Level 2

Likes

6 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile
khushbooa339108
Level 2

18-12-2018

Hi Veena,

Thanks for replying!

I am using AEM 6.4.2.0. I have all per-requisites installed and have already followed all steps for project setup described in Chapter 1 and have been following all steps in subsequent chapters as well. I am not sure why I am still getting this error, I don't see anything described in the tutorial missing from my configurations. Do you have any other pointers to proceed?

I am getting similar errors in creating any other model component as well. I am stuck with these errors for so long now and would really appreciate getting some help to resolve them.

Thanks,

Khushboo

Avatar

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile
chrisatsirius
Level 2

06-09-2019

I found this and I applied to my wknd and it worked for me:

https://youtu.be/lKWHsVh1hRA

Avatar

Avatar
Boost 1
Level 1
matth39107775
Level 1

Like

1 like

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Applaud 5
View profile

Avatar
Boost 1
Level 1
matth39107775
Level 1

Like

1 like

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Applaud 5
View profile
matth39107775
Level 1

03-09-2019

Since my issue was slightly different I just ended up making a separate post

Byline cannot be resolved to a type using WKND tutorial

Avatar

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Boost 3
Level 2
chrisatsirius
Level 2

Likes

4 likes

Total Posts

6 posts

Correct Reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile
chrisatsirius
Level 2

03-09-2019

I m still trying to figure out what and where the issue is.

Avatar

Avatar
Boost 1
Level 1
matth39107775
Level 1

Like

1 like

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Applaud 5
View profile

Avatar
Boost 1
Level 1
matth39107775
Level 1

Like

1 like

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Applaud 5
View profile
matth39107775
Level 1

03-09-2019

Yeah I have

<core.wcm.components.version>2.5.0</core.wcm.components.version>

and

   <dependency>

   <groupId>com.adobe.cq</groupId>

   <artifactId>core.wcm.components.core</artifactId>

   <version>2.5.0</version>

   <scope>provided</scope>

   </dependency>

in my pom.xml but still have the same error

Avatar

Avatar
Boost 1
Level 1
matth39107775
Level 1

Like

1 like

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Applaud 5
View profile

Avatar
Boost 1
Level 1
matth39107775
Level 1

Like

1 like

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
Applaud 5
View profile
matth39107775
Level 1

03-09-2019

What did you update in your configurations? Are you referring to the pom.xml files?

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,406 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,406 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

19-12-2018

thanks for posting your fix!

Avatar

Avatar
Validate 1
Level 10
edubey
Level 10

Likes

273 likes

Total Posts

1,502 posts

Correct Reply

392 solutions
Top badges earned
Validate 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Validate 1
Level 10
edubey
Level 10

Likes

273 likes

Total Posts

1,502 posts

Correct Reply

392 solutions
Top badges earned
Validate 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
edubey
Level 10

18-12-2018

1. Can you attach the package for community?

2. Did you try Troubleshooting steps here

https://helpx.adobe.com/experience-manager/kt/sites/using/getting-started-wknd-tutorial-develop/part...

Avatar

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

449 likes

Total Posts

1,024 posts

Correct Reply

116 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

449 likes

Total Posts

1,024 posts

Correct Reply

116 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile
Veena_Vikram
MVP

18-12-2018

What is the version of AEM you are using? . Make sure the below prerequisites are met

The following is required:

  1. Java 1.8
  2. Apache Maven (3.3.9 or newer)
  3. AEM 6.4 + Service Pack 2 or
  4. AEM 6.3 + Service Pack 3
  5. Eclipse or other IDE

Getting Started with AEM Sites Chapter 1 - Project Setup