AEM 6.3 - Maven build is successful but still doesn't install content

See this article - it will help you -- Developing your first Experience Manager 6.3 Components

Hi,

Yes Scott is right. We have the article that shows how to create the project using Lazybones and build using Maven: Developing your first Experience Manager 6.3 Components

Also, Eclipse plugin is very good to communicate with experience manager as described in the article.

Hope this helps!!

~Ratna.

Thank you for the response. I have followed this article before. Haven't been able to find anything useful yet related to the issue I am facing. Please let me know if you think I am missing something here.

Are you able to get the article successfully completed? Or you can get this article working - but cannot apply the same concept to your project?

Thank you for the response. I have created the project using the same steps. Although, I would expect the build process to install all the content in CRXde. Currently, only the project folder structure is being deployed to the CRXde, all the components, clientlibs, editable templates etc, none of them gets installed to CRXde. This is the issue I am facing. When I do the Maven build through eclipse/cmd prompt, all it does is it install the project structure with folders minus any components, templates, clientlibs etc.

When you import from Eclipse into AEM JCR - you should be seeing:

I have completed the article successfully and used lazybones to create the project. Normally, I create the components, clientlibs etc in CRXde and then export them to local filesystem/eclipse and commit it to GIt. I checked out the project from Git on a different machine, did a maven build in the hopes of seeing all my components/templates etc in CRXd which didn't happen. Only the project structure with empty folders got deployed to CRXde.

                                                                 To look further into the issue, I created a test component in CRXde, exported it into eclipse using vlt up and then ran a build again only to find out that the test component wasn't deployed to CRXde. Although, I could see that test component in the zip created by the maven build.

Hi,

Try the below steps and let me know

a) Create the project in your local using Lazybone and get the project installed in AEM instance

b) Now check in crxde AEM for the project created with required folders(like components,config,src,install,templates)

c) Now create the required components and templates using crxde.

d) Now using Eclipse Vault Plugin do vault import, so that all your components and templates gets synched up with local.

e) Now you can modify any component if needed in eclipse and do a lazy bone build and install to AEM.

I suspect the reason why you dont see components inside crxde is may be you are not including the components in filter.xml appropriately.I too had same kind of issue once and started using eclipse vault plugin which made life easy for synching to local and build back to AEM.

Hope this helps.

Regards,

Raja

Ratna is testing this again - he has many times in past. He will update this thread soon,

Hi Rajashankar,

Here is the filter.xml

<?xml version="1.0" encoding="UTF-8"?>

<workspaceFilter version="1.0">

    <filter root="/apps/aem-site"/>

    <filter root="/apps/sling/servlet/errorhandler"/>

    <filter root="/conf/aem-site" mode="merge"/>

    <filter root="/etc/clientlibs/aem-site"/>

</workspaceFilter>

Do you think I am missing something here ?

I am using Eclipse neon, and the eclipse vault plugin doesn't work on this version. So, I am using the filevault through command line to export the component to local filesystem. Can you please let me know what version of eclipse you are using ?

Also, even if somehow I get the vault plugin to work, it is expected that the maven build installs everything. I am not sure if this is filevault messing things up or something else.