Closed ashlyjose closed 9 years ago
@ashlyjose - thanks for the report. I have a couple of questions
1) How did you import this project? Is it an exact copy of the project that your colleague has set up?
I'm asking because sometimes when sharing via source control Eclipse files ( .project/.classpath/.settings ) are not added .
2) Please attach a screenshot of the project facets. You can find it by right-clicking on the project, selecting properties and then navigating to the 'Project Facets' property page.
3) What version of the AEM developer tools do you use?
File -> Import -> Maven -> Existing Maven Projects
Thanks for the info. So it seems that the facets are correctly set. What have you tried and does not work?
Ok, now at this point, although the facets are correctly set, project is not displayed properly in eclipse, meaning I cannot see anything in the JCR Properties when I click on the imported project (components, pages, templates etc..). Also, I see the xml files in Eclipse directly (dialog.xml). Please find the screenshot below.
Also, I cannot add the ui.apps project to my local AEM server. It does allow me to add the project using "Add and Remove" option right clicking the server, but nothing happens. I have also tried right clicking on the project AEM -> Export to server - this also does not work
In short, How do I get the project on to my local AEM server linked to Eclipse project so that I can see and edit the JCR Properties from eclipse?
Could you try the following:
This should now trigger the project to run in the AEM context...
@mikeyhendy Thanks Michael. It works !!
@rombert The workaround specified by Michael works and I'm able to get things running. Do you want me to leave this issue open for a proper fix for this or is this the way it is supposed to work?
@mikeyhendy - thanks for digging up the root cause!
@ashlyjose - Please leave it open, we need to find a better UI for this. For now I'm considering adding an error marker on the project if the 'jcr_root' folder can not be found
The improvement has been added in the Sling IDE Tooling project ( see SLING-4000: Add error marker on the project when content sync root does not exist ) and will be incorporated in the next AEM Developer Tools public release.
If you'd like to build a fix yourself, please follow the instructions from Sling IDE Tooling - building from source.
Not sure if it is the wrong way I'm doing it, but how to get existing project up and running with AEM Developer Tools for Eclipse?
My colleague has set up a project using AEM Developer Tools plugin for Eclipse and now I need that project setup in my Eclipse, with deploying it to my local AEM 6 instance.
When I import the project to my workspace as Maven project, it is imported properly, but I cant get the plugin identify the project. It is just a maven project !
Also, options for "Convert to Bundle project" and "Convert to Content project" is disabled.
I'm (whole team) stuck here and can't progress. Is this a bug? If not, what is the correct way of performing this task?