May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19886) Template parameters that don't have a value defined display as 'generated'

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19886?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19886: ------------------------------------- Labels: application_wizard v3 (was: ) > Template parameters that don't have a value defined display as 'generated' > -------------------------------------------------------------------------- > > Key: JBIDE-19886 > URL: https://issues.jboss.org/browse/JBIDE-19886 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Labels: application_wizard, v3 > Fix For: 4.3.0.Beta1 > > > While loading template https://github.com/jboss-openshift/application-templates/blob/master/eap/... the GIT_URI value does not provide a value and it displays as 'generated'. It should default to some value. Additionally any parameter that does not have a value attribute should be required; we should not allow moving on in the wizard unless required values are fulfilled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[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, 9 months

1
0
0 / 0

[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: ----------------------------------------- True. I may build a job anyway, as much to locally test with the svn update site so your help much appreciated. Will ping accordingly. Otherwise, on their mailing lists now so will monitor over the course of the next fortnight or so. > 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} >  > <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, 9 months

1
0
0 / 0

[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: ------------------------------------ OK, as long as `DIRSTUDIO-1023: Generate P2 repository / update site` gets done sooner-rather-than-later I guess you're good here. If the story changes, my offer still stands to help set up publishing from your new Jenkins-pulls-from-SVN-directly job. > 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} >  > <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, 9 months

1
0
0 / 0

[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: ----------------------------------------- Just received a reply from their mailing list pointing at the following [message|http://mail-archives.apache.org/mod_mbox/directory-dev/201505.mbo...]. Looks like a hold-our-horses and it should be sooner-rather-than-later. > 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} >  > <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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19711: ------------------------------------ Core as an optional "Web Tools" feature, or Core as "installed OOTB when you hit Eclipse Marketplace or use the *Abridged JBoss Tools* category on the update site"? Please clarify. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[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} >  > <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, 9 months

1
0
0 / 0

[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} >  > <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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19886) Template parameters that don't have a value defined display as 'generated'

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19886?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19886: ------------------------------------- Fix Version/s: 4.3.0.Beta1 Sprint: Sprint #4 May 2015 Affects Version/s: 4.3.0.Beta1 (was: 4.3.x) > Template parameters that don't have a value defined display as 'generated' > -------------------------------------------------------------------------- > > Key: JBIDE-19886 > URL: https://issues.jboss.org/browse/JBIDE-19886 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta1 > > > While loading template https://github.com/jboss-openshift/application-templates/blob/master/eap/... the GIT_URI value does not provide a value and it displays as 'generated'. It should default to some value. Additionally any parameter that does not have a value attribute should be required; we should not allow moving on in the wizard unless required values are fulfilled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19886) Template parameters that don't have a value defined display as 'generated'

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19886: ------------------------------------- Summary: Template parameters that don't have a value defined display as 'generated' Key: JBIDE-19886 URL: https://issues.jboss.org/browse/JBIDE-19886 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Jeff Cantrill Priority: Minor While loading template https://github.com/jboss-openshift/application-templates/blob/master/eap/... the GIT_URI value does not provide a value and it displays as 'generated'. It should default to some value. Additionally any parameter that does not have a value attribute should be required; we should not allow moving on in the wizard unless required values are fulfilled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2015