May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22448) TP p2diff generation fails build when TP version changes

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22448?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22448: ---------------------------------------- TP now build successfully again (after a build with p2diff.skip=true). Should we close this issue or do we plan more brainstorming as part of this sprint? > TP p2diff generation fails build when TP version changes > -------------------------------------------------------- > > Key: JBIDE-22448 > URL: https://issues.jboss.org/browse/JBIDE-22448 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > Add support for skipping p2diff generation when there's no previous site against which to diff, eg., when upversioning or releasing from snapshot to release in Nexus. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-221) Exception when debugging with chromium [EBZ#494731]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-221: --------------------------------------- Summary: Exception when debugging with chromium [EBZ#494731] Key: ERT-221 URL: https://issues.jboss.org/browse/ERT-221 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Fix For: Neon (4.6) RC3 Using EPP JavaScript RC2 package, using "Debug As > Node.js application" on some random file. This error seems to happen whenever the program is interrupted, for example because a dependency doesn't compile or whatever. Such remote interruption can happen pretty often, the shouldn't be treated as IDE error, but rather caught and presented to the user. Currently, it's logged in the IDE, and AERI suggests to open a ticket for that despite there is nothing wrong in the IDE. This gives an impression that debugger has bugs and this is going to flood AERI with no fair reason. -- eclipse.buildId=4.6.0.I20160519-1730 java.version=1.8.0_77 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.javascript.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.javascript.product org.eclipse.wst.jsdt.chromium.debug.core Error Fri May 27 11:23:55 CEST 2016 SDK:org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection: Exception in message listener java.lang.IllegalStateException: Connection not attached at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.checkAttached(SocketConnection.java:455) at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.send(SocketConnection.java:416) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$V8CommandOutputImpl.send(StandaloneVmImpl.java:249) at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:133) at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:1) at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.send(BaseCommandProcessor.java:75) at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.sendV8CommandAsync(V8CommandProcessor.java:84) at org.eclipse.wst.jsdt.chromium.internal.v8native.DebugSession.sendMessageAsync(DebugSession.java:101) at org.eclipse.wst.jsdt.chromium.internal.v8native.processor.AfterCompileProcessor.messageReceived(AfterCompileProcessor.java:44) at org.eclipse.wst.jsdt.chromium.internal.v8native.DefaultResponseHandler.handleResponseWithHandler(DefaultResponseHandler.java:60) at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:145) at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:1) at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:112) at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:115) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:116) at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:122) at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:211) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22454: ------------------------------------- Summary: Application Wizard: Build configuration wizard page has redundant environment variables table Key: JBIDE-22454 URL: https://issues.jboss.org/browse/JBIDE-22454 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha3 Reporter: Marián Labuda In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22454?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22454: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application Wizard: Build configuration wizard page has redundant environment variables table > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22454 > URL: https://issues.jboss.org/browse/JBIDE-22454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22453) Application Wizard: Environment variables located on 2 wizard pages

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22453?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22453: ---------------------------------- Summary: Application Wizard: Environment variables located on 2 wizard pages (was: Application Wizard: Shell to add and edit environment variable have different labels for name) > Application Wizard: Environment variables located on 2 wizard pages > ------------------------------------------------------------------- > > Key: JBIDE-22453 > URL: https://issues.jboss.org/browse/JBIDE-22453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, docker, openshift_v3 > > In New OpenShift Application wizard with selected builder image there is a table containing environment variables on the Build Configuration wizard page. When adding a new variable by clicking on Add... button, shell to add is opened with labels "Name:" and "Value:". When editing an environment variable on the same wizard page, there are different labels in edit env. var shell. Environment variable name is labeled as "Environment Variable:" and value as "Value:". It should be same for both dialogs, I would recommend labels Name and Value. > Same table with buttons seems to be used also in deploy docker image wizard, there is same flaw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22453) Application Wizard: Application Wizard: Shell to add and edit environment variable have different labels for name

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22453?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22453: ---------------------------------- Summary: Application Wizard: Application Wizard: Shell to add and edit environment variable have different labels for name (was: Application Wizard: Environment variables located on 2 wizard pages) > Application Wizard: Application Wizard: Shell to add and edit environment variable have different labels for name > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22453 > URL: https://issues.jboss.org/browse/JBIDE-22453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, docker, openshift_v3 > > In New OpenShift Application wizard with selected builder image there is a table containing environment variables on the Build Configuration wizard page. When adding a new variable by clicking on Add... button, shell to add is opened with labels "Name:" and "Value:". When editing an environment variable on the same wizard page, there are different labels in edit env. var shell. Environment variable name is labeled as "Environment Variable:" and value as "Value:". It should be same for both dialogs, I would recommend labels Name and Value. > Same table with buttons seems to be used also in deploy docker image wizard, there is same flaw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22453) Application Wizard: Shell to add and edit environment variable have different labels for name

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22453?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22453: ---------------------------------- Summary: Application Wizard: Shell to add and edit environment variable have different labels for name (was: Application Wizard: Application Wizard: Shell to add and edit environment variable have different labels for name) > Application Wizard: Shell to add and edit environment variable have different labels for name > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22453 > URL: https://issues.jboss.org/browse/JBIDE-22453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, docker, openshift_v3 > > In New OpenShift Application wizard with selected builder image there is a table containing environment variables on the Build Configuration wizard page. When adding a new variable by clicking on Add... button, shell to add is opened with labels "Name:" and "Value:". When editing an environment variable on the same wizard page, there are different labels in edit env. var shell. Environment variable name is labeled as "Environment Variable:" and value as "Value:". It should be same for both dialogs, I would recommend labels Name and Value. > Same table with buttons seems to be used also in deploy docker image wizard, there is same flaw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22453) Application Wizard: Shell to add and edit environment variable have different labels for name

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22453?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22453: ---------------------------------- Labels: application_wizard docker openshift_v3 (was: ) > Application Wizard: Shell to add and edit environment variable have different labels for name > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22453 > URL: https://issues.jboss.org/browse/JBIDE-22453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, docker, openshift_v3 > > In New OpenShift Application wizard with selected builder image there is a table containing environment variables on the Build Configuration wizard page. When adding a new variable by clicking on Add... button, shell to add is opened with labels "Name:" and "Value:". When editing an environment variable on the same wizard page, there are different labels in edit env. var shell. Environment variable name is labeled as "Environment Variable:" and value as "Value:". It should be same for both dialogs, I would recommend labels Name and Value. > Same table with buttons seems to be used also in deploy docker image wizard, there is same flaw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22453) Application Wizard: Shell to add and edit environment variable have different labels for name

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22453: ------------------------------------- Summary: Application Wizard: Shell to add and edit environment variable have different labels for name Key: JBIDE-22453 URL: https://issues.jboss.org/browse/JBIDE-22453 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha3 Reporter: Marián Labuda Priority: Minor In New OpenShift Application wizard with selected builder image there is a table containing environment variables on the Build Configuration wizard page. When adding a new variable by clicking on Add... button, shell to add is opened with labels "Name:" and "Value:". When editing an environment variable on the same wizard page, there are different labels in edit env. var shell. Environment variable name is labeled as "Environment Variable:" and value as "Value:". It should be same for both dialogs, I would recommend labels Name and Value. Same table with buttons seems to be used also in deploy docker image wizard, there is same flaw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-722) Fix JDG test and revert wrong fix for UDF import

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/JBTIS-722?page=com.atlassian.jira.plugin.... ] Matus Makovy updated JBTIS-722: ------------------------------- Fix Version/s: (was: 4.2.7.Final) > Fix JDG test and revert wrong fix for UDF import > ------------------------------------------------ > > Key: JBTIS-722 > URL: https://issues.jboss.org/browse/JBTIS-722 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016