Re: Empty Folders outside the Filter do not Deploy in Eclipse IDE

[Robert Munteanu <ro...@apache.org>]

Hi Andy,

On Mon, 2015-06-29 at 15:37 -0700, Andreas Schaefer Sr. wrote:
> I tried to fix this issue by just accepting the parent if a 
> .content.xml file was found but that failed later in the 
> ItemDefintionProviderImpl.getQNodeDefinition() where it was not able 
> to find the Default Primary Type.
> 
> Because a package can be installed without the .content.xml files I 
> am not sure what is missing in the code but right now I am just 
> asking the user to create the folders / install the package 
> beforehand.

Sounds like a bug to me, can you please file a JIRA issue about it?

Thanks,

Robert

> 
> - Andy
> 
> > On Jun 26, 2015, at 4:39 PM, Andreas Schaefer Sr. <schaefera@me.com
> > > wrote:
> > 
> > When I was testing the Eclipse AEM/Sling IDE Tooling Plugin with 
> > the Adobe ACS Tools I found a scenario where the deployment of 
> > content fails.
> > 
> > This is the scenario:
> > 
> > /jcr_root
> > 	.content.xml
> > 	/apps
> > 		.content.xml
> > 		/cq
> > 			/core
> > 				/content
> > 					.content.xml
> > 					/nav
> > 
> > Deploying this structure onto AEM 6.0 works like a charm but 
> > deploying with the Eclipse IDE Tooling Plugin fails with an 
> > CoreException stating that no matching Child Node definition found 
> > for ‘cq'.
> > 
> > The reason is that the ResourceChangeCommandFactory method 
> > findSerliazationDataFromCoveringParent() at the very end the code 
> > is checking if the repositoryPath is covered by the ResourceProxy 
> > but it isn’t because there is no .xontent.xml for that folder 
> > (/apps/cq). Even if I add that folder to the .content.xml inside 
> > the /apps folder it won’t work because it also needs properties.
> > 
> > I can fix that issue by creating /apps/cq and /apps/cq/core as 
> > Folders and /apps/core/content as Sling OrdererFolder.
> > 
> > So is that a known issue and the users needs to deploy a content 
> > module first through Maven? If not is that a bug for which I can 
> > create a ticket.
> > 
> > Attached is the project I used to test it. It is a slimmed down 
> > copy of the AEM ACS Tools in which I did change the group and 
> > artifact id to avoid conflicts. These are the steps:
> > 
> > - Fire up a clean / empty AEM 6.0
> > - Open Eclipse with a new Workspace
> > - Import the attached Maven Project
> > - Setup a Server Connection
> > - Convert the sub module to a Sling Content Package
> > - Add the Module to the build
> > - Start the Server in Run Mode
> > - Publish
> > 
> > With the fix mentioned above or with a manual deployment first I 
> > can deploy just fine.
> > 
> > Cheers - Andy Schaefer<parent.folder.creation.issue.zip>
>