[
https://issues.apache.org/jira/browse/SLING-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-5268:
-----------------------------------
Fix Version/s: (was: Sling Eclipse IDE 1.2.2)
Sling Eclipse IDE 1.2.4
> Make Sling Connector IDE Independent
> ------------------------------------
>
> Key: SLING-5268
> URL: https://issues.apache.org/jira/browse/SLING-5268
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Andreas Schaefer
> Priority: Major
> Fix For: Sling Eclipse IDE 1.2.4
>
>
> Sling Connector code in the IDE Tooling needs to be IDE independent to make
> it possible to be used in other IDEs like IntelliJ, NetBeans etc. There are
> two main areas:
> 1) Modules should not contain OSGi references as for example IntelliJ does
> not use OSGi internally. IDE can wrap a module inside OSGi but shouldn't
> require it.
> 2) Code that is used to check or deploy resources on Sling should be IDE
> independent. For example ResourceChangeCommandFactory should not be using
> I-classes from Eclipse but rather Interfaces that can be implemented by any
> IDE to their requirements.
> The main reason for doing this is to ease the adoption of new code from this
> project as well as making it easier for new IDE to adopt.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
