You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2014/05/14 18:01:17 UTC
[jira] [Commented] (SLING-3559) Never run project launches when
publishing
[ https://issues.apache.org/jira/browse/SLING-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997689#comment-13997689 ]
Stefan Egli commented on SLING-3559:
------------------------------------
[~rombert], for content projects agreed. For bundle projects we had the launch mechanism as a fall-back when the deployment mechanism is configured not to use the tooling.support.install bundle, no?
> Never run project launches when publishing
> ------------------------------------------
>
> Key: SLING-3559
> URL: https://issues.apache.org/jira/browse/SLING-3559
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The SlingLaunchpadBehaviour still runs project launches if they exist. I don't think that's needed anymore, as the content sync code should be good enough, and launches are reserved for other tasks. As such, we should remove that code.
> [~egli] - is there anything that I missed?
--
This message was sent by Atlassian JIRA
(v6.2#6252)