[JBoss JIRA] (JBIDE-19887) BRMS and Fuse examples should be hidden if Integration Stack is not available
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-19887:
-----------------------------------
Summary: BRMS and Fuse examples should be hidden if Integration Stack is not available
Key: JBIDE-19887
URL: https://issues.jboss.org/browse/JBIDE-19887
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Affects Versions: 4.3.0.Beta1
Reporter: Fred Bricon
For BRMS and Fuse examples, the connectors requirements would let a user believe the proper features can be installed, but this is only true if the integration stack is available. If it's not, then an error would pop up as the missing connectors would not be installable.
We could check if jboss.discovery.site.integration-stack.url is empty and hide all examples containing a BRMS or FUSE tag
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19845) Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19845?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19845:
-------------------------------------
Summary: Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view (was: Creating a new OpenShift application via Configure context menu of a project always use first connection from OpenShift Explorer view)
> Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19845
> URL: https://issues.jboss.org/browse/JBIDE-19845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
>
> If user wants to create a new OpenShift application via context menu of a project, it is possible to do it via context menu "Configure - New/Import OpenShift application". Previously this selection prompted user to choose desired connection where to create a new application. Nowadays the first existing connection in OpenShift explorer view is selected and it is not possible to change connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-19820:
------------------------------------------
Mars M7 632,691,651,638 = 653s
M7 + batch feature 792,750,726,800 = 767s
M7 + CDI feature 778, 738 = 758s
(M6 + CDI was 794,712 = 753s)
There's some improvement for batch for sure (and also if you take into consideration that M7 seems to be slower than M6)
> Batch feature makes wildfly import way slower
> ---------------------------------------------
>
> Key: JBIDE-19820
> URL: https://issues.jboss.org/browse/JBIDE-19820
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies.
> I did a 4 runs with following results:
> M6 was able to import WF 628,575,577,612 (in seconds) = average 598s
> M6 with batch feature: 843,832,924,877 (in seconds) = average 869s
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19808:
------------------------------------
I would +1 the idea of your creating a new job in Jenkins to build from https://svn.apache.org/repos/asf/directory/studio/trunk/, then use our new rsync.sh script to publish the bits into some folder like /updates/requirements/2.0.0.timestamp-SNAPSHOT.
If you set up the build part of the job, I can set up the publishing part for you. Then you'll have something you can use to re-build their trunk as needed, until such time as they start regularly publishing their own snapshots / releases. And you'll have fresh bits for your TP, so the blocked JIRAs can move forward.
> 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: build.xml, 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:* http://download.jboss.org/jbosstools/updates/requirements/apache-director...
> *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- Eliminated the dependency
> {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 Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ]
Paul Richardson commented on JBIDE-19808:
-----------------------------------------
Well, I have 5 JIRAs that currently depend on this going into the TP. Work on the LDAP importer was also explicitly requested. Therefore, it would be good to have it sooner-rather-than-later if you catch my drift.
On the other hand, I was unwilling to suggest using their sources since I thought that was discouraged since we are mirroring releases. That's said sources build, tests pass locally and obviously I will thoroughly test prior to depending on it so if use of the sources is an option then I am all for it!
> 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: build.xml, 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:* http://download.jboss.org/jbosstools/updates/requirements/apache-director...
> *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- Eliminated the dependency
> {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