[
https://issues.apache.org/jira/browse/SLING-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736834#comment-13736834
]
Stefan Egli commented on SLING-3009:
------------------------------------
>From a first-round look at libra it seems to do rather similar things as we
>have to do with the sling bundle support indeed. I think this needs some more
>research as to how/if we want to make use of libra. If we use it, sling ide
>tooling basically becomes an extension of libra and it might also replace lot
>of existing code (eg sling.content facet type, slinglaunchpadserver). As a
>detail I noticed that libra doesn't seem to use maven projects ootb - but
>instead for example creates an explicit META-INF/MANIFEST.MF (while we
>typically store that info in the pom.xml) - but maybe libra could be fiddled
>with to work nicely with maven too, I suppose...
> [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
