[jira] [Resolved] (SLING-3009) [Tooling] support auto-deploy of osgi bundles from eclipse to a running sling launchpad

["Stefan Egli (JIRA)" <ji...@apache.org>]

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

Stefan Egli resolved SLING-3009.
--------------------------------

    Resolution: Fixed

implemented bundle-deployment. There are two modes now, which can be configured on the (wst) server:
 (1) mvn sling:install
 (2) using sling.tooling.support.install-bundle (SLING-3019), a POST to that servlet is done, which in turn takes the exploded files from /target/classes and installs the bundle. This variant only works if the server runs on localhost
                
> [Tooling] support auto-deploy of osgi bundles from eclipse to a running sling launchpad
> ---------------------------------------------------------------------------------------
>
>                 Key: SLING-3009
>                 URL: https://issues.apache.org/jira/browse/SLING-3009
>             Project: Sling
>          Issue Type: New Feature
>          Components: IDE
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Sling Eclipse IDE 1.0.0
>
>
> From Eclipse, for a bundle type maven project, it should be possible to auto-deploy the built bundle into the configured sling launchpad. Ideally, but optionally, we'd have hot-code replacement of individual classes of that bundle. But auto redeploying the entire bundle is fine as a start.
> We should look into such tools like Eclipse libra (http://www.eclipse.org/libra/) or Spring-Loaded (https://github.com/SpringSource/spring-loaded) for help on redeploy/hotcode replacement

--
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