April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25616: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.6.x > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25684) Import Application Wizard: label "Checkout branch XXXX" is cropped

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25684?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25684: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Import Application Wizard: label "Checkout branch XXXX" is cropped > ------------------------------------------------------------------ > > Key: JBIDE-25684 > URL: https://issues.jboss.org/browse/JBIDE-25684 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Priority: Minor > Labels: import_wizard > Fix For: 4.6.x > > Attachments: image-2018-02-02-16-58-52-735.png > > > See last text "Check out branch ma" (for master) > !image-2018-02-02-16-58-52-735.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22138: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Fred Bricon > Labels: openshift_v3, server_adapter > Fix For: 4.6.x > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21448: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Port Forwarding: Allow port-forwarding of ports not defined on pod metadata > --------------------------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.6.x > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25857) Add support for images import/export in CDK/minishift adapter

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25857?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25857: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Add support for images import/export in CDK/minishift adapter > ------------------------------------------------------------- > > Key: JBIDE-25857 > URL: https://issues.jboss.org/browse/JBIDE-25857 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.5.3.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, cdk_server_adapter, minishift > Fix For: 4.6.x > > > Would be fine if we could manage images export/import for the CDK/Minishift server adapter. This is how it could be implemented: > * in the UI we could display the list of available images (using the Docker connection) > * in the UI we could also display the list of cached images (from the minishift images list command) > Then using context menu we could import/export images when one of them is selected -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25905: ------------------------------- Fix Version/s: 4.6.x (was: 4.6.0.AM1) > [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25905 > URL: https://issues.jboss.org/browse/JBIDE-25905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.6.x > > Attachments: service-ports.gif, services-routing-page-no-labels.png, services-routing-page.png > > > [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard. > Service Ports table starts to behave awkward after reset. > steps: > # ASSERT: have a docker image available that exposes several ports (ex. registry.access.redhat.com/openshift3/ose-haproxy-router:v3.7.14 which exposes 4 ports) > # EXEC: in Docker Explorer: select your docker image and pick "Deploy to OpenShift..." from the context menu > # ASSERT: "Deploy Image to OpenShift" wizard shows up > # EXEC: get to the "Services & Routing Settings" page > # ASSERT: all ports are listed, a port is checked in column "Used by route" > !services-routing-page.png! > # EXEC: hit "Reset" (and confirm the dialog that asks you if you want to reset the ports) > # EXEC: click in the column "Used by route" on the 2nd port (or any unchecked entry) > Result: > Labels for columns "Name", "Service Port", "Pod Port" disappear > !services-routing-page-no-labels.png! > !service-ports.gif! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25509) Properties: one can not select multiple resources

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25509?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25509: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.3.Final) > Properties: one can not select multiple resources > ------------------------------------------------- > > Key: JBIDE-25509 > URL: https://issues.jboss.org/browse/JBIDE-25509 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: properties > Fix For: 4.6.x > > > steps: > # ASSERT: have an OpenShift app running > # EXEC: in OpenShift explorer: select the project and open up the "Properties" view. In the properties view select "Pods" > # ASSERT: there are multiple pods listed > # EXEC: try to select several ones (ex. in order to delete them) > Result: > You can only select a single entry, you cannot select several ones and ex. delete them at once. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25826) Connection wizard: resizing hides authentication details

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25826?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25826: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Connection wizard: resizing hides authentication details > -------------------------------------------------------- > > Key: JBIDE-25826 > URL: https://issues.jboss.org/browse/JBIDE-25826 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.6.x > > Attachments: image-2018-03-20-10-55-32-002.png > > > steps: > # EXEC: launch connection wizard > # EXEC: decrease the size of the dialog so that parts of the *Authetication* details are hidden > Result: > !image-2018-03-20-10-55-32-002.png! > The authentication details are not visible and there are no scrollbars to scroll those into the visible area. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25866) Schema files for WildFly 12 are missing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25866?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25866: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Schema files for WildFly 12 are missing > --------------------------------------- > > Key: JBIDE-25866 > URL: https://issues.jboss.org/browse/JBIDE-25866 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.6.x > > > I accidentally found out that schema files that are new in WildFly 12 haven't been added to org.jboss.tools.as.catalog plugin, for instance jboss-web_12_0.xsd (I'm not sure if there are more). > Why I found out is that I was just trying to verify and close this older JIRA: > JBIDE-25102 Add "jboss-web-11_0.xsd" to catalog > And since then we now have WildFly 12 too. > So this is something to keep in mind when adding a new server adapter. > Also, please check if this needs to be added to https://github.com/robstryker/jboss.org.schema too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25838: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.3.Final) > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: connection, explorer > Fix For: 4.6.x > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018