[ 
https://issues.apache.org/jira/browse/SLING-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778937#comment-13778937
 ] 

Robert Munteanu commented on SLING-3120:
----------------------------------------

Further fixes as part of 
http://svn.apache.org/viewvc?view=revision&revision=1526588

- separated the artifacts into a org.apache.sling.ide.artifacts bundle. This 
bundle now allows access to the tooling support bundle ( for now )
- installation now works from the server view as well as from the bundle 
creation wizard

Still to be done:

- find out how to make the OSGiClientFactory a SCR component in the api bundle 
without adding hard requirement to equinox bundles 
- refresh the servers view after the bundle is installed
- set the tooling support bundle version when creating a server programatically 
using the bundle creation wizard
                
> Allow installing/updating the install support bundle from the servers view
> --------------------------------------------------------------------------
>
>                 Key: SLING-3120
>                 URL: https://issues.apache.org/jira/browse/SLING-3120
>             Project: Sling
>          Issue Type: Improvement
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.0
>
>
> Currently the only way to install the support/install bundle is if we're 
> creating a new server when creating a new bundle. this option should be 
> available from the server editor page.
> Implementation plan:
> * Extract an OSGiClient and make it part of API/Core
> * Create an OSGiClientFactory and make it a SCR component+service
> * Make access to the archetype resources public, probably as part of a 
> separate bundle ( a follow-up bug should make this bundle contain all 
> embedded resources )
> * Implement bundle install in the server page, maybe with special logic for 
> SNAPSHOTs

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

Reply via email to