maven dependencies for com.adobe.cq.sightly.WCMUse and io.sightly.java.api.Use | Community
Skip to main content
Dinu_Arya
Level 6
October 16, 2015
Solved

maven dependencies for com.adobe.cq.sightly.WCMUse and io.sightly.java.api.Use

  • October 16, 2015
  • 3 replies
  • 4437 views

Hi,

Do we have the maven dependencies for WCMUse and Use? I have searched but they are not available in the adobe/nexus repositories. When will we get them? Instead of writing JAVA class under the component, I would like to make them as different bundles (so that I can use some features of eclipse while programming like auto suggestions given by eclipse IDE whe we press ctrl+space) and want to use them in <component>.html.

Thanks,

Arya

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 Feike_Visser1

here you go...

            <dependency>

                <groupId>com.adobe.aem</groupId>

                <artifactId>aem-api</artifactId>

                <version>6.0.0.1</version>

                <scope>provided</scope>

            </dependency>

You only need one :-)

best,
Feike

3 replies

Feike_Visser1
Adobe Employee
Feike_Visser1Adobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

here you go...

            <dependency>

                <groupId>com.adobe.aem</groupId>

                <artifactId>aem-api</artifactId>

                <version>6.0.0.1</version>

                <scope>provided</scope>

            </dependency>

You only need one :-)

best,
Feike

Dinu_Arya
Dinu_AryaAuthor
Level 6
October 16, 2015

Hi Feike,

At the time you have given they are not in the repository. I got error whenever I added the above dependency in pom.xml. Now its working fine and I'm able to make the sightly related java files into a separate bundle they are working properly through sightly rendering logic.

Thanks,

AryA.

Feike_Visser1
Adobe Employee
Adobe Employee
October 16, 2015

Weird, because it is quite long already available as you can see via this url:

http://repo.adobe.com/nexus/content/groups/public/com/adobe/aem/aem-api/

Anyway, good that it is working now!