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 2014/10/11 00:19:34 UTC
[jira] [Commented] (SLING-4025) Investigate fully deploying content
packages on server startup/module deployment
[ https://issues.apache.org/jira/browse/SLING-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167655#comment-14167655 ]
Robert Munteanu commented on SLING-4025:
----------------------------------------
Fixed in https://svn.apache.org/viewvc?view=revision&revision=1631002
> 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)