No suitable archetypes found | Community
Skip to main content
J
jotoo
New Participant
October 16, 2015
Solved

No suitable archetypes found

  • October 16, 2015
  • 13 replies
  • 8776 views
I am trying to get an AEM-eclipse-maven development environment configured.  I have followed the steps provided here - http://docs.adobe.com/docs/en/dev-tools/aem-eclipse.html.  When attempting to create a sample project I found that I have no archetypes available.  

Steps to recreate

1. Select File > New > Project

2. Select AEM > AEM Sample Multi-Mode Project

3. Select Next

4. In the Choose Project Location and Archetype window the following error message is shown.    "No suitable archetypes found. Please make sure that the proper maven repositories are configured and indexes are up to date."

Eclipse version is Kepler.  Installed software -- AEM Developer Tools, Maven Integration for Eclipse, Sling IDE Tools, Sling IDE Tools - M2e based

 

 

    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 Lokesh_Shivalingaiah

    Hi J,

    Please refer this [1]. I have written in detail on this issue. Let me know if you need any more details

     [1] http://adobeaemclub.com/configuring-aem-maven-archetype-for-eclipse-plugin/

    13 replies

    Show previous replies
    K
    Kanwaljit
    New Participant
    October 16, 2015

    So, I have two different outcomes on two different systems.

    In office one, I use local arch type. I see the issue. Only difference is that I am behind proxy. In home system, I do not see the issue. Here I did not need to give the local arch type file.

    I'll try in office system with some debugging and see if it helps. Any pointers will be helpful.

    /Regards
    Kanwal

    yoanns60676056
    yoanns60676056
    New Participant
    October 16, 2015

    It's maybe because of the proxy but when I set it up, it doesn't work anywaaays.

    Lokesh_Shivalingaiah
    Lokesh_Shivalingaiah
    New Participant
    October 16, 2015

    yeaa.. thats because of the proxy. you can set the proxy in eclipse and see if that works

      Terms & ConditionsAccessibility statement

      Loading footer...