You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/01/17 21:37:04 UTC
[jira] [Updated] (SLING-6092) Create OSGi-only development feature
[ https://issues.apache.org/jira/browse/SLING-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-6092:
-----------------------------------
Fix Version/s: (was: Sling Eclipse IDE 1.2.0)
Sling Eclipse IDE 1.2.2
> Create OSGi-only development feature
> ------------------------------------
>
> Key: SLING-6092
> URL: https://issues.apache.org/jira/browse/SLING-6092
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Robert Munteanu
> Priority: Minor
> Fix For: Sling Eclipse IDE 1.2.2
>
>
> For some scenarios - mostly backend-only work - it can be useful to install a stripped down variation of the IDE Tooling which only provides the OSGi support for publishing bundles and debugging.
> Splitting off the code into a new feature and probably a new bundle should not be too hard, but we need to handle the upgrade scenario so that when upgrading to a post-split version all required bundles are installed.
> Also, the Eclipse Marketplace listing would need to be updated to make the new feature a mandatory one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)