June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22447) Explorer: Concurrent modification when scaling to a large number of pods

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22447?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22447: ------------------------------- Story Points: 4 > Explorer: Concurrent modification when scaling to a large number of pods > ------------------------------------------------------------------------ > > Key: JBIDE-22447 > URL: https://issues.jboss.org/browse/JBIDE-22447 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > > When you scale a service from 1 to a large number (100), then the Openshift explorer is refreshed many times and ConcurrentModification may occur. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22447) Explorer: Concurrent modification when scaling to a large number of pods

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22447?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22447: ---------------------------------- Assignee: Jeff MAURY > Explorer: Concurrent modification when scaling to a large number of pods > ------------------------------------------------------------------------ > > Key: JBIDE-22447 > URL: https://issues.jboss.org/browse/JBIDE-22447 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > > When you scale a service from 1 to a large number (100), then the Openshift explorer is refreshed many times and ConcurrentModification may occur. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22442) Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22442?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22442: ------------------------------------ Maybe a Windows case. Will recheck > Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22442 > URL: https://issues.jboss.org/browse/JBIDE-22442 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.x > > > When managing forwarding ports, select/unselecting the 'Find free local ports' checkbox makes the UI being unresponsive for several seconds and OS (Windows10 in my case) displaying 'Application not responding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3947: ------------------------------ Description: Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though. !vagrant.png|thumbnail! The issue might be connected to the fact that with these versions the command {noformat}where vagrant{noformat} in fact returns 2 files was: Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. It tries to download and install its own though. !vagrant.png|thumbnail! The issue might be connected to the fact that with these versions the command {noformat}where vagrant{noformat} in fact returns 2 files > Some older versions of vagrant skip version validation > ------------------------------------------------------ > > Key: JBDS-3947 > URL: https://issues.jboss.org/browse/JBDS-3947 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Attachments: vagrant.png > > > Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though. > !vagrant.png|thumbnail! > The issue might be connected to the fact that with these versions the command > {noformat}where vagrant{noformat} > in fact returns 2 files -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-743) Guvnor is still available on the update site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-743?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-743. ------------------------------ Fix Version/s: 10.0.0.Alpha1 Resolution: Done This should be corrected with the latest 10.0.0.Alpha1-SNAPSHOT > Guvnor is still available on the update site > -------------------------------------------- > > Key: JBTIS-743 > URL: https://issues.jboss.org/browse/JBTIS-743 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.0.0.Alpha1 > > > The following update site > http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > contains Guvnor feature which should be removed in Neon release (like ESB and jBPM3). > Note that the feature is not included in any category but it is available if you uncheck 'Group items by category'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-742) Update Teiid Designer in Devstudio IS 10.0.0.Alpha1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-742?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-742. ------------------------------ Fix Version/s: 10.0.0.Alpha1 Resolution: Done Updated TD in 10.0.0.Alpha1-SNAPSHOT ref: Greetings, A new Alpha1 snapshot build for the 10.0.0 Red Hat Developer Studio Integration Stack is available for QE testing. The updated components are BPMN2 Modeler and Teiid Designer. These bits are not for public consumption - this is just a snapshot of Alpha1 for QE testing baseline purposes - not the Alpha1 itself. * Released .Final components None * Early Access components BPEL 1.3.200.Final > BPMN2 1.3.0.Final_1.3.0.Final_neon DROOLS/JBPM6 6.4.1.Final FUSE TOOLING 8.0.0.Beta2 MODESHAPE 3.8.0.Beta1 # SWITCHYARD 2.1.0.Beta3 (unavailable in this snapshot) > TEIID DESIGNER 10.0.1.Beta1 10.0.0.Alpha1-SNAPSHOT, 4.4.0.Alpha1-SNAPSHOT 1. If installing from Eclipse Neon: - install 'Red Hat Developer Studio 10.0.0.Alpha1' Update site: http://download.jboss.org/jbosstools/neon/staging/updates/ 2. Start devstudio or eclipse-with-rhds from step 1, then: Help > Install New Software... Add... - use this for 'Location:' for the integration stack: https://devstudio.redhat.com/10.0/staging/updates/integration-stack/early... # early access components Done! JBoss Central is supported: * Specify the integration stack discovery artifact: -vmargs \ -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.Alpha1-SNAPSHOT/earlyaccess/devstudio-directory.xml \ -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.Alpha1-SNAPSHOT/ \ -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.Alpha1-SNAPSHOT/earlyaccess/ The standard Eclipse installer is available for community IS: * Install JBoss Tools 4.4.0.Alpha1: - install 'JBoss Tools 4.4.0.Alpha1' Update site: http://download.jboss.org/jbosstools/neon/staging/updates/ * Start eclipse-with-jboss-tools, then: Help > Install New Software... Add... - use this for 'Location:' for the integration stack: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... # early access components JBoss Central is supported for JBTIS: * Install JBoss Tools 4.4.0.Alpha1: - install 'JBoss Tools 4.4.0.Alpha1' Update site: http://download.jboss.org/jbosstools/neon/staging/updates/ * Specify the integration stack discovery artifacts: ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/neon/staging/updates/integration-stack/discovery/4.4.0.Alpha1-SNAPSHOT/earlyaccess/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/neon/staging/updates/integration-stack/discovery/4.4.0.Alpha1-SNAPSHOT \ -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/neon/staging/updates/integration-stack/discovery/4.4.0.Alpha1-SNAPSHOT/earlyaccess Offline zip files are supported for both production and community installs: 1. https://devstudio.redhat.com/10.0/staging/updates/integration-stack/devst... (MD5) 2. http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... (MD5) For component and QE test developers - the JBTIS target platforms are: - Full and candidate release target platforms including early access dependencies: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Al... --paull > Update Teiid Designer in Devstudio IS 10.0.0.Alpha1 > --------------------------------------------------- > > Key: JBTIS-742 > URL: https://issues.jboss.org/browse/JBTIS-742 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: build, teiid > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.0.0.Alpha1 > > > Please update the version of Teiid Designer to 10.0.1.Beta1 in Devstudio IS 10.0.0.Alpha1-SNAPSHOT. My point is not to have older version of TD in Neon (TD 10.0.0.Beta3) than in Mars (TD 10.0.1.Beta1). > Moreover, this will help QE to use the same tests for both Mars and Neon at the moment. Currently, this is not possible since there is a different 'New Project' wizard in TD 10.0.1.Beta1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation

by Jan Richter (JIRA)

Jan Richter created JBDS-3947: --------------------------------- Summary: Some older versions of vagrant skip version validation Key: JBDS-3947 URL: https://issues.jboss.org/browse/JBDS-3947 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.0.0.GA Reporter: Jan Richter Assignee: Denis Golovin Attachments: vagrant.png Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. It tries to download and install its own though. !vagrant.png|thumbnail! The issue might be connected to the fact that with these versions the command {noformat}where vagrant{noformat} in fact returns 2 files -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22442) Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22442?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22442: ----------------------------------------- Tried it on my Fedora 23. Everything is ok, no such effect. > Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22442 > URL: https://issues.jboss.org/browse/JBIDE-22442 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.x > > > When managing forwarding ports, select/unselecting the 'Find free local ports' checkbox makes the UI being unresponsive for several seconds and OS (Windows10 in my case) displaying 'Application not responding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-747) Add more smoke tests to drools tests suite

by Tomas David (JIRA)

Tomas David created JBTIS-747: --------------------------------- Summary: Add more smoke tests to drools tests suite Key: JBTIS-747 URL: https://issues.jboss.org/browse/JBTIS-747 Project: JBoss Tools Integration Stack Issue Type: Task Components: drools/ jBPM, QE Reporter: Tomas David Assignee: Tomas David Priority: Minor Add new smoke tests or mark existing to be smoke tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-20387. --------------------------------- > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.3.0.Beta2 > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.0.Alpha1 > > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016