[
https://issues.apache.org/jira/browse/SLING-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167658#comment-14167658
]
Robert Munteanu commented on SLING-4025:
----------------------------------------
To be more precise, modules are fully published if deployed to a running
server, but not if deployed when the server is stopped, even after the server
is started. This is standard WST behaviour. It seems that a manual call to
publish 'flushes' the pending changes, but I haven't found a way to do it
automatically.
> Investigate fully deploying content packages on server startup/module
> deployment
> --------------------------------------------------------------------------------
>
> Key: SLING-4025
> URL: https://issues.apache.org/jira/browse/SLING-4025
> Project: Sling
> Issue Type: Task
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.2
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.4
>
>
> After a discussion with [~justinedelson] I believe that the current behaviour
> of not publishing content modules on server startup/on adding them to the
> server can be counter-intuitive.
> I'll investigate reverting the changes done for SLING-3081 for this release,
> and see if it's feasible from a performance point of view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
