[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ]
Paul Richardson updated JBIDE-19808:
------------------------------------
Attachment: p2.diff
A p2.diff executed with the following command is attached, where the mirror was created using a clone of the build.xml script outlined in the mirroring instructions.
{code}
./p2diff file:///home/phantomjinx/programming/java/tdesigner/ldap/mirror/0.1.0-SNAPSHOT http://download.jboss.org/jbosstools/updates/development/luna/ > p2.diff
{code}
Thus, all plugins being brought in by the apache update site are denoted by "<".
I do refer to a specific feature since the apache directory update site is constructed differently from normal. It only contains the features with no normal layout of artifacts/content/plugins/features.
I have listed the plugins I actually use in the JIRA since there is no reason that we could not pull only those (just not sure whether it would work with the current update site or not).
The plugins do carry their own perspective and BrowserView. I was trying to avoid them by not including the plugin org.apache.directory.studio.ldapbrowser.ui but unfortunately some resources are required when refresh the BrowserWidget. Odd I know, but an exception was produced when it was not included.
As far as eclipse plugins are concerned, versions are not specified in manifests or feature.xml files hence the plugins are happy to use existing luna plugins.
> 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
> Attachments: p2.diff
>
>
> *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)
10 years, 11 months
[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ]
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)
10 years, 11 months
[JBoss JIRA] (JBTIS-418) Cannot install JBDS-IS from downloaded zip into JBDS when offline
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-418?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-418:
-----------------------------
Fix Version/s: 8.0.3.GA
(was: 8.0.2.CR1)
> Cannot install JBDS-IS from downloaded zip into JBDS when offline
> -----------------------------------------------------------------
>
> Key: JBTIS-418
> URL: https://issues.jboss.org/browse/JBTIS-418
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: releng
> Affects Versions: 8.0.0.GA
> Environment: Linux x86_64 Open JDK 7
> JBDS 8.0.0.GA-v20141020-1042-B317
> JBDS IS 8.0.0.GA
> Reporter: Denis Golovin
> Assignee: Paul Leacu
> Fix For: 8.0.3.GA
>
>
> While was testing possible solutions for including JBDS IS into JBDS Installer I realized that there something missing in JBDS or IS zip. Offfline installation into JBDS 8.0.0.GA fails with
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Data Virtualization Development (ModeShape, Teiid Designer) 8.0.0.201502201745 (com.jboss.devstudio.integration-stack.ds.feature.feature.group 8.0.0.201502201745)
> Missing requirement: JBoss Data Virtualization Development (ModeShape, Teiid Designer) 8.0.0.201502201745 (com.jboss.devstudio.integration-stack.ds.feature.feature.group 8.0.0.201502201745) requires 'org.jboss.tools.usage.feature.feature.group 0.0.0' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18494) Importing EAP "jboss-logging" quickstart raises errors
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18494?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-18494.
---------------------------------
Resolution: Partially Completed
Partially Resolved as latest quickstart is fixed but there's nothing we can do about older versions.
> Importing EAP "jboss-logging" quickstart raises errors
> ------------------------------------------------------
>
> Key: JBIDE-18494
> URL: https://issues.jboss.org/browse/JBIDE-18494
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects - select the quickstart
> The error raised is:
> The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path home.jsp /jboss-logging/src/main/webapp line 1 JSP Problem
> (This can be fixed by adding Maven Managed Dependencies to the Java Build path)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19542) Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19542?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19542:
------------------------------------
I think all we need is the *com.atlassian.connector.eclipse* feature, as per the install guide [1]:
{code}
./eclipse -nosplash -application org.eclipse.equinox.p2.director -repository http://update.atlassian.com/atlassian-eclipse-plugin/rest/nightly/e3.7 -installIU com.atlassian.connector.eclipse.feature.group{code}
[1] https://confluence.atlassian.com/display/IDEPLUGIN/Installing+the+Eclipse...
> Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19542
> URL: https://issues.jboss.org/browse/JBIDE-19542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.3.Final
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Minor
>
> Steps to recreate the error:
> * Install Eclipse (eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz)
> * Configure JBoss Tools as an update site (http://download.jboss.org/jbosstools/updates/staging/luna/)
> * Install JBoss Tools Common - Mylyn (3.6.2.Final-v20150325-0456-B99, org.jboss.tools.common.mylyn.feature.feature.group)
> * Whenever eclipse is started, this error is written to the .log
> ============================================================================
> cat .log
> !SESSION 2015-03-31 14:33:50.481 -----------------------------------------------
> eclipse.buildId=4.4.2.M20150204-1700
> java.version=1.7.0_55
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> ============================================================================
> Workaround:
> * From JBoss Central, install: "Mylyn Issue Tracker Connectors"
> * This results in the following packages being installed
> * Mylyn Commons 3.14.2.v20150217-2244 org.eclipse.mylyn.commons.feature.group
> * Mylyn Context Connector: Eclipse IDE 3.14.2.v20150218-0125 org.eclipse.mylyn.ide_feature.feature.group
> * Mylyn Context Connector: Java Development 3.14.2.v20150218-0125 org.eclipse.mylyn.java_feature.feature.group
> * Mylyn Context Connector: Plug-in Development 3.14.2.v20150218-0125 org.eclipse.mylyn.pde_feature.feature.group
> * Mylyn Context Connector: Team Support 3.14.2.v20150218-0125 org.eclipse.mylyn.team_feature.feature.group
> * Mylyn Task List 3.14.2.v20150217-2341 org.eclipse.mylyn_feature.feature.group
> * Mylyn Task-Focused Interface 3.14.2.v20150218-0125 org.eclipse.mylyn.context_feature.feature.group
> * Mylyn Tasks Connector: Bugzilla 3.14.2.v20150217-2341 org.eclipse.mylyn.bugzilla_feature.feature.group
> * Mylyn Versions 1.6.2.v20150217-2249 org.eclipse.mylyn.versions.feature.group
> After installing this^, the error is not generated
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18494) Importing EAP "jboss-logging" quickstart raises errors
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18494?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-18494 at 5/14/15 1:29 PM:
--------------------------------------------------------------
So jboss-logging for 6.4.0.GA, which is fixed, shows up in Central now, but also does the one for 6.3.0.GA.
BTW both appear in http://www.jboss.org/developer-materials/#!sys_type=jbossdeveloper_quicks...
I've added product/version tags in Central to distinguish them (cc [~burrsutter]) :
!http://content.screencast.com/users/fbricon/folders/Jing/media/8ec3aaff-bad5-4462-817e-1f3812d27435/00000105.png|width=700px!
See JBIDE-19809
was (Author: fbricon):
So jboss-logging for 6.4.0.GA, which is fixed, shows up in Central now, but also does the one for 6.3.0.GA.
BTW both appear in http://www.jboss.org/developer-materials/#!sys_type=jbossdeveloper_quicks...
I've added product/version tags in Central to distinguish them (cc [~burrsutter]) :
!http://content.screencast.com/users/fbricon/folders/Jing/media/8ec3aaff-bad5-4462-817e-1f3812d27435/00000105.png|width=700px!
> Importing EAP "jboss-logging" quickstart raises errors
> ------------------------------------------------------
>
> Key: JBIDE-18494
> URL: https://issues.jboss.org/browse/JBIDE-18494
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects - select the quickstart
> The error raised is:
> The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path home.jsp /jboss-logging/src/main/webapp line 1 JSP Problem
> (This can be fixed by adding Maven Managed Dependencies to the Java Build path)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months