April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3827) JBDS installation fails when (windows) user has non-ascii chars in the name

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3827: ------------------------------ Fix Version/s: 11.0.0.AM1 > JBDS installation fails when (windows) user has non-ascii chars in the name > --------------------------------------------------------------------------- > > Key: JBDS-3827 > URL: https://issues.jboss.org/browse/JBDS-3827 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3, 11.0.0.AM1 > > > I have created a user named Pakoň and tried to install everything into the default folder. JBDS failed with: > {noformat}Fri, 15 Apr 2016 12:38:40 GMT-ERROR: jbds - Error: Command failed: c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true -jar C:\WINDOWS\7zS9F06.tmp\jbds.jar C:\Users\Pakoň\AppData\Local\Temp\jbds-autoinstall.xml > - ERROR - > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.<init>(FileInputStream.java:138) > at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(AutomatedInstaller.java:564) > at com.izforge.izpack.installer.AutomatedInstaller.<init>(AutomatedInstaller.java:86) > at com.izforge.izpack.installer.Installer.main(Unknown Source){noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: DEV_MODE and DEBUG are inconsistent btw. nodejs and eap

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24185: ---------------------------------------- Summary: Server adapter: DEV_MODE and DEBUG are inconsistent btw. nodejs and eap Key: JBIDE-24185 URL: https://issues.jboss.org/browse/JBIDE-24185 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.AM2 Reporter: Andre Dietisheim * eap ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. {code} "com.redhat.dev-mode": "DEBUG:true", {code} ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label {code} "com.redhat.dev-mode.port": "DEBUG_PORT:8787" {code} ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* {code} "com.redhat.dev-mode": "DEV_MODE:false", "com.redhat.dev-mode.port": "DEBUG_PORT:5858", {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24184: ------------------------------------- Fix Version/s: 4.4.4.AM3 > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys are hard-coded, not read from docker image > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.4.AM3 > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24184: ------------------------------------- Summary: Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image (was: Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys are hard-coded, not read from docker image) > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.4.AM3 > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24184: ---------------------------------------- Summary: Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys are hard-coded, not read from docker image Key: JBIDE-24184 URL: https://issues.jboss.org/browse/JBIDE-24184 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.AM2 Reporter: Andre Dietisheim to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: * nodejs {code} "Labels": { ... "com.redhat.dev-mode": "DEV_MODE:false", "com.redhat.dev-mode.port": "DEBUG_PORT:5858", ... {code} * eap {code} "Labels": { ... "com.redhat.dev-mode": "DEBUG:true", "com.redhat.dev-mode.port": "DEBUG_PORT:8787", ... {code} Our code on the other hand is hard-coding these, not reading the keys from the docker image: {code} public class OpenShiftDebugUtils { private static final String DEBUG_KEY = "DEBUG"; private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; ... {code} {code} public class OpenShiftLaunchController extends AbstractSubsystemController implements ISubsystemController, ILaunchServerController { ... private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ ... {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23769) New Application: Do not throw exception in error log when provided template is of wrong kind.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23769?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23769: ------------------------------- Story Points: 8 > New Application: Do not throw exception in error log when provided template is of wrong kind. > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23769 > URL: https://issues.jboss.org/browse/JBIDE-23769 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.4.AM3 > > > When creating new application from local template one selects wrong file (not of kind "Template", but kind "Pod" for example) multiple (same) exceptions are thrown into error log: > {noformat} > !ENTRY org.eclipse.core.databinding 4 0 2017-01-19 13:56:20.472 > !MESSAGE Unhandled exception: Wrong resource kind: Pod > !STACK 0 > org.jboss.tools.openshift.internal.ui.wizard.newapp.NotATemplateException: Wrong resource kind: Pod > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalAppSource(NewApplicationWizardModel.java:139) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadAppSource(NewApplicationWizardModel.java:293) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$17.run(ApplicationSourceListPage.java:824) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think it's enough to inform the user in the wizard (this is already happening). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23656) Missing validation of step listener with empty attribute ref

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23656?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23656: ------------------------------- Story Points: 10 > Missing validation of step listener with empty attribute ref > ------------------------------------------------------------ > > Key: JBIDE-23656 > URL: https://issues.jboss.org/browse/JBIDE-23656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.Final > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.4.AM3 > > Attachments: batch-test-project.zip > > > There is missing warning in listener's tag with empty reference in source view. Empty value of reference attribute in step listener should show warning like job listener does when there is empty ref: "Job listener is expected". Please, add warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24145) Command to tune memory requirements for a deployement

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24145?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24145: ------------------------------- Story Points: 15 > Command to tune memory requirements for a deployement > ----------------------------------------------------- > > Key: JBIDE-24145 > URL: https://issues.jboss.org/browse/JBIDE-24145 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4231) OpenShift Explorer sometimes don't show the objects in Properties view

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4231?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4231: ----------------------------- Story Points: 10 > OpenShift Explorer sometimes don't show the objects in Properties view > ---------------------------------------------------------------------- > > Key: JBDS-4231 > URL: https://issues.jboss.org/browse/JBDS-4231 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.2.0.GA > Environment: * JBoss Developer Studio 10.2.0.GA > * CDK > Reporter: Ricardo Martinelli Oliveira > Assignee: Jeff MAURY > Fix For: 10.4.0.AM3 > > > After right-click in a project in OpenShift Explorer view and select Properties, not always the list of Kubernetes/OpenShift objects are listed in the Properties view. The workaround I found is close all editors, the Properties view and after changing the focus on other views, go back to OpenShift Explorer and Refresh it I can finally list the objects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23656) Missing validation of step listener with empty attribute ref

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23656?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23656: ------------------------------- Sprint: devex #130 April 2017 > Missing validation of step listener with empty attribute ref > ------------------------------------------------------------ > > Key: JBIDE-23656 > URL: https://issues.jboss.org/browse/JBIDE-23656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.Final > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.4.AM3 > > Attachments: batch-test-project.zip > > > There is missing warning in listener's tag with empty reference in source view. Empty value of reference attribute in step listener should show warning like job listener does when there is empty ref: "Job listener is expected". Please, add warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2017