[jbosstools-issues] [JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068171#comment-13068171 ] 

Max Rydahl Andersen commented on JBIDE-19808:
---------------------------------------------

In the TP your are referring to very specific feature - would it be better to just depend on the absolute necessary plugins ?

Does these plugins add their own additional ldap view/persectives or will just purely include enough to get the ldap widgets for teiid's use ?

can you make a p2diff showing the actual complete set of plugins/dependencies it drags in compared to current TP ? (i.e. one could expect by a 2 year old release that it would drag in Kepler or older eclipse core libraries)


> Teiid Designer would like to depend on org.apache.directory.studio plugins
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-19808
>                 URL: https://issues.jboss.org/browse/JBIDE-19808
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: target-platform, teiid
>    Affects Versions: 4.2.3.Final
>            Reporter: Paul Richardson
>            Assignee: Barry LaFond
>
> *Reason:*
> Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478].
> The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense.
> The current working implementation of Teiid with this widget can be found here:
> https://github.com/phantomjinx/teiid-designer/tree/ldap-studio
> The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits.
> *Project page/sources:*
> * [directory.apache.org|https://directory.apache.org]
> * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk]
> * [udpate site | http://directory.apache.org/studio/update/2.x/]
> *Version:* 2.0.0
> *License and owner:* Apache licence and Foundation
> *Original p2 repo:* http://directory.apache.org/studio/update/2.x/
> *JBoss mirror:*
> *Include Sources:* Not available from existing update site but may well be in the next release.
> *Affected projects:* Teiid Designer
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> * org.apache.directory.api.ldap.model
> * org.apache.directory.studio.common.core
> * org.apache.directory.studio.common.ui
> * org.apache.directory.studio.connection.core
> * org.apache.directory.studio.connection.ui
> * org.apache.directory.studio.ldapbrowser.common
> * org.apache.directory.studio.ldapbrowser.core
> * org.apache.directory.studio.ldapbrowser.ui
> {code}
>     <!-- Needed by Teiid Designer for support with ldap browsing UI -->
>     <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
>       <repository location="http://directory.apache.org/studio/update/2.x/"/>
>       <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/>
>     </location>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)