[ 
https://issues.apache.org/jira/browse/SLING-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237285#comment-15237285
 ] 

Robert Munteanu commented on SLING-5652:
----------------------------------------

Thanks for the sample project. However, this 'works for me'. Here's what I've 
done

# Imported the SLING5652 project in my Eclipse workspace
# Started a new AEM server ( since the project references the {{cq}} namespace )
# Added the module to the server

Export was successful. Another attempt

# Deleted /content/sling5652 using CRXDE Lite
# Right-clicked the project in the Project Explorer
# Selected AEM -> Export to Server
# Clicked Finish

This was also successful. Do you have other steps to reproduce? If this works 
for you, can you please:

# let me know your JVM version + OS
# upload debug + trace logs as per 
https://sling.apache.org/documentation/development/ide-tooling.html#gathering-debug-information
 


> Publishing content fails if intermediate nodes are not present in the 
> repository
> --------------------------------------------------------------------------------
>
>                 Key: SLING-5652
>                 URL: https://issues.apache.org/jira/browse/SLING-5652
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.1.0
>            Reporter: Graham
>            Assignee: Robert Munteanu
>         Attachments: sling5652.zip
>
>
> I'm seeing the issue https://issues.apache.org/jira/browse/SLING-3586 with 
> Sling Eclipse IDE 1.1.0
> The error is
> Failed exporting: JcrResult[ success:false, exception: 
> org.apache.sling.ide.transport.RepositoryException - 
> javax.jcr.RepositoryException: No parent found at 
> /content/sling5652/en/thankyou/jcr:content/image/file ; it's needed to create 
> node at /content/sling5652/en/thankyou/jcr:content/image/file/jcr:content] 
> Is it possible that this has creeped back in?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to