[jira] [Commented] (SLING-3081) Do not re-publish modules when starting the launchpad for the first time
[
https://issues.apache.org/jira/browse/SLING-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999759#comment-13999759
]
Robert Munteanu commented on SLING-3081:
{quote}The new-project-wizard will also start the server of course and
up-till-now was assuming the publish would automatically start. That we can
still trigger explicitly from the wizard though, so no issue there.{quote}
Sounds good
> Do not re-publish modules when starting the launchpad for the first time
>
>
> Key: SLING-3081
> URL: https://issues.apache.org/jira/browse/SLING-3081
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Reporter: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> This results in unnecessary publishing activity. The right way is to provide
> a manual action to sync a sub-tree to ( or the whole module ) to the
> Launchpad.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3081) Do not re-publish modules when starting the launchpad for the first time
[
https://issues.apache.org/jira/browse/SLING-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999758#comment-13999758
]
Robert Munteanu commented on SLING-3081:
{quote}The new-project-wizard will also start the server of course and
up-till-now was assuming the publish would automatically start. That we can
still trigger explicitly from the wizard though, so no issue there.{quote}
Sounds good
> Do not re-publish modules when starting the launchpad for the first time
>
>
> Key: SLING-3081
> URL: https://issues.apache.org/jira/browse/SLING-3081
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Reporter: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> This results in unnecessary publishing activity. The right way is to provide
> a manual action to sync a sub-tree to ( or the whole module ) to the
> Launchpad.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3081) Do not re-publish modules when starting the launchpad for the first time
[ https://issues.apache.org/jira/browse/SLING-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998538#comment-13998538 ] Stefan Egli commented on SLING-3081: Agreed, might make it more light-weight to just 'connect' instead of 'full publish'. If the user knows that the 'connect to server' button doesn't imply an initial publish, then all things are fine. If we get user feedback about this being odd we could still add a config parameter to the server about this. But having it off by default sounds good. The new-project-wizard will also start the server of course and up-till-now was assuming the publish would automatically start. That we can still trigger explicitly from the wizard though, so no issue there. > Do not re-publish modules when starting the launchpad for the first time > > > Key: SLING-3081 > URL: https://issues.apache.org/jira/browse/SLING-3081 > Project: Sling > Issue Type: Bug > Components: IDE >Reporter: Robert Munteanu > Fix For: Sling Eclipse IDE 1.0.2 > > > This results in unnecessary publishing activity. The right way is to provide > a manual action to sync a sub-tree to ( or the whole module ) to the > Launchpad. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3081) Do not re-publish modules when starting the launchpad for the first time
[ https://issues.apache.org/jira/browse/SLING-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998100#comment-13998100 ] Robert Munteanu commented on SLING-3081: [~egli] - When SLING-2651 is fixed, I'm tempted to fix this one for 1.0.0 as well. The reason is that for external servers it's confusing to connect it to the workspace and instantly publish all the assigned modules. This can even take a long time for large modules ( think vlt ci every time you start Eclipse ... ) . Thoughts? > Do not re-publish modules when starting the launchpad for the first time > > > Key: SLING-3081 > URL: https://issues.apache.org/jira/browse/SLING-3081 > Project: Sling > Issue Type: Bug > Components: IDE >Reporter: Robert Munteanu > Fix For: Sling Eclipse IDE 1.0.2 > > > This results in unnecessary publishing activity. The right way is to provide > a manual action to sync a sub-tree to ( or the whole module ) to the > Launchpad. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3081) Do not re-publish modules when starting the launchpad for the first time
[ https://issues.apache.org/jira/browse/SLING-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773006#comment-13773006 ] Robert Munteanu commented on SLING-3081: This only happens the first time the server is started and it's published as a full change: SlingLaunchpadBehaviour.publishModule(PUBLISH_FULL, CHANGED, [Module[sling-vlt-project-13,org.apache.sling.ide.contentModuleFactory:sling-vlt-project-13]]) As such, this is not critical for the 1.0.0 release. > Do not re-publish modules when starting the launchpad for the first time > > > Key: SLING-3081 > URL: https://issues.apache.org/jira/browse/SLING-3081 > Project: Sling > Issue Type: Bug > Components: IDE >Reporter: Robert Munteanu >Assignee: Robert Munteanu > Fix For: Sling Eclipse IDE 1.0.2 > > > This results in unnecessary publishing activity. The right way is to provide > a manual action to sync a sub-tree to ( or the whole module ) to the > Launchpad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
