You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2015/02/19 23:44:13 UTC

[jira] [Updated] (SLING-4091) Non-Java content is not deployed if the connection is made in debug mode

     [ https://issues.apache.org/jira/browse/SLING-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-4091:
-----------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.1.0)
                   Sling Eclipse IDE 1.0.8

> Non-Java content is not deployed if the connection is made in debug mode
> ------------------------------------------------------------------------
>
>                 Key: SLING-4091
>                 URL: https://issues.apache.org/jira/browse/SLING-4091
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.4
>            Reporter: Robert Munteanu
>            Priority: Minor
>             Fix For: Sling Eclipse IDE 1.0.8
>
>
> If we connect to the server in debug mode we rely on the debug connection to update changes to Java files. This means that changes to non-java files, e.g. content files deployed with the JCR content loader will not be published.



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