August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-23030: ---------------------------------- Git Pull Request: https://github.com/openshift/openshift-restclient-java/pull/205, https://github.com/jbosstools/jbosstools-openshift/pull/1294 (was: https://github.com/openshift/openshift-restclient-java/pull/205) > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22888) update the versions of SVNKit and Subclipse we bundle in Red Hat Central

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22888?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-22888: --------------------------------------- I think Eclipse freezes because of an issue in the org.eclipse.egit.ui plugin. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=500230 > update the versions of SVNKit and Subclipse we bundle in Red Hat Central > ------------------------------------------------------------------------ > > Key: JBIDE-22888 > URL: https://issues.jboss.org/browse/JBIDE-22888 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central-update, target-platform, updatesite > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > We could consider updating the versions of SVNKit and Subclipse we bundle in Red Hat Central. > > Currently we have: > * Subclipse 1.10.9 / clientadapter 1.10.3 > * svnkit 1.8.10 (supports up to svn 1.8) > Latest: > * Subclipse 1.12 > * svnkit 1.8.12 (supports up to svn 1.9 - http://svn.svnkit.com/repos/svnkit/tags/1.8.12/CHANGES.txt) > > Reason to update: https://developer.jboss.org/message/961176?et=watches.email.thread#961176 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-387) JSON editor "supports" comments, not supported by JSON [EBZ#499705]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-387?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-387: ------------------------------- Assignee: Snjezana Peco (was: Ilya Buziuk) > JSON editor "supports" comments, not supported by JSON [EBZ#499705] > ------------------------------------------------------------------- > > Key: ERT-387 > URL: https://issues.jboss.org/browse/ERT-387 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > > I tried commenting a line in a JSON file using the common syntax "/* comment */": > /*"jquery/jquery-min": "1.12",*/ > This caused the line to become blue, so I figured JSON must support comments. But as mentioned in https://en.wikipedia.org/w/index.php?title=JSON&oldid=734431215 this is not the case. > Ticket #495578 explains that Angelo ZERR decided to support "JSON comments" since .jshintrc (no idea what that is) uses it. In my opinion, this should be disabled by default, but for sure, it should be possible to disable. Currently, all JSON highlights are mandatory (the checkboxes are disabled). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22765) In FTL file in editor are missing directives in code assistant

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22765?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22765: -------------------------------------- Assignee: Daniel Dekany (was: Alexey Kazakov) > In FTL file in editor are missing directives in code assistant > -------------------------------------------------------------- > > Key: JBIDE-22765 > URL: https://issues.jboss.org/browse/JBIDE-22765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160715-2233-B5663 > Build date: 20160715-2233 > Reporter: Ondrej Dockal > Assignee: Daniel Dekany > Priority: Critical > Fix For: 4.4.1.Final > > > In .ftl file when using <# and opening code assistant, there are missing directives: compress, nt and setting. I checked http://freemarker.org/docs/ref_directive_alphaidx.html for supported directives but did not find any reason we are missing those mentioned above. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-842) Improve the stability of SwitchYard debugger tests

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-842?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-842. ----------------------------------- pushed to master > Improve the stability of SwitchYard debugger tests > -------------------------------------------------- > > Key: JBTIS-842 > URL: https://issues.jboss.org/browse/JBTIS-842 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, switchyard > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.3.1.Final > > > It seems that the Breakpoints view sometimes disable the button 'Remove All Breakpoints' even if there is at least one breakpoint. The stacktrace is as follows > {code} > org.jboss.reddeer.swt.exception.SWTLayerException: SWT Shell passed to constructor is null. The following shells are available > class org.eclipse.swt.widgets.Shell with text 'Debug - org.switchyard.handlers.ValidateHandler - JBoss Developer Studio' > at org.jboss.reddeer.swt.impl.shell.AbstractShell.<init>(AbstractShell.java:34) > at org.jboss.reddeer.swt.impl.shell.DefaultShell.<init>(DefaultShell.java:24) > at org.jboss.tools.switchyard.reddeer.debug.BreakpointsView.removeAllBreakpoints(BreakpointsView.java:47) > at org.jboss.tools.switchyard.ui.bot.test.DebuggerDebuggingTest.removeAllBreakpoints(DebuggerDebuggingTest.java:86) > {code} > To workaround this just close and reopen the Breakpoints view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-19536: --------------------------------------- I experienced the same issue in devstudio: Version: 10.1.0.GA Build id: GA-v20160823-0457-B5835 Build date: 20160823-0457, nothing is really happening around this issue, I post a comment in eclipse bugzilla... > Infinite job loop when creating project > --------------------------------------- > > Key: JBIDE-19536 > URL: https://issues.jboss.org/browse/JBIDE-19536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.4.x > > Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump, workspace_jbds9_endless_building_loop.rar > > > Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974 > I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-23030: --------------------------------------- [~fbricon] Updated the restclient 5.1 snapshot to have a fix, can jbt be updated to depend on snapshot or does this need to be backported into a 5.0.0? > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4015) Only one MSI installer can be running at the same time

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4015?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4015: -------------------------------- Story Points: 3 > Only one MSI installer can be running at the same time > ------------------------------------------------------ > > Key: JBDS-4015 > URL: https://issues.jboss.org/browse/JBDS-4015 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 64-bit > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.1.0.GA > > > Currently with cygwin detection and OpenJDK component uses MSI installer there is running two msi installers at the same time. If that happens only one that starts first succeed all other fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22765) In FTL file in editor are missing directives in code assistant

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22765?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22765: ---------------------------------------- [~ddekany] please take a look. > In FTL file in editor are missing directives in code assistant > -------------------------------------------------------------- > > Key: JBIDE-22765 > URL: https://issues.jboss.org/browse/JBIDE-22765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160715-2233-B5663 > Build date: 20160715-2233 > Reporter: Ondrej Dockal > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.Final > > > In .ftl file when using <# and opening code assistant, there are missing directives: compress, nt and setting. I checked http://freemarker.org/docs/ref_directive_alphaidx.html for supported directives but did not find any reason we are missing those mentioned above. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-4014: -------------------------------------- [~akurtako]: The main class we use for usage tracking - https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/o... Some docs how to use it: https://github.com/jbosstools/jbosstools-devdoc/blob/master/api/usage/usa... The code which we use to report the product ID - https://github.com/jbosstools/jbosstools-base/blob/e0b10e225f070bc11aa1bf... > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBDS-4014 > URL: https://issues.jboss.org/browse/JBDS-4014 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 10.2.0.AM1 > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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