July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26235) Add telemetry events

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26235: ---------------------------------- Summary: Add telemetry events Key: JBIDE-26235 URL: https://issues.jboss.org/browse/JBIDE-26235 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-server-protocol Affects Versions: 4.9.0.AM1 Reporter: Jeff MAURY Assignee: Rob Stryker Fix For: 4.9.x Define telemetry events that may be of interest. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26117: ------------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.x) > Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) > ----------------------------------------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.9.0.AM2 > > > The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi... > Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection: > The Eclipse > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26117: ------------------------------------- Sprint: devex #153 August 2019 > Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) > ----------------------------------------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.9.0.AM2 > > > The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi... > Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection: > The Eclipse > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26165) Implement a Launcher project wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26165?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26165: ---------------------------------- Assignee: Jeff MAURY > Implement a Launcher project wizard > ----------------------------------- > > Key: JBIDE-26165 > URL: https://issues.jboss.org/browse/JBIDE-26165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.9.0.AM2 > > > Implements a Launcher based project wizard using the implemented model -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26165) Implement a Launcher project wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26165?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26165: ------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.x) > Implement a Launcher project wizard > ----------------------------------- > > Key: JBIDE-26165 > URL: https://issues.jboss.org/browse/JBIDE-26165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.9.0.AM2 > > > Implements a Launcher based project wizard using the implemented model -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26165) Implement a Launcher project wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26165?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26165: ------------------------------- Sprint: devex #153 August 2019 > Implement a Launcher project wizard > ----------------------------------- > > Key: JBIDE-26165 > URL: https://issues.jboss.org/browse/JBIDE-26165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.9.0.AM2 > > > Implements a Launcher based project wizard using the implemented model -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26147) Incremental publish not working with WF13, WF12 and WF11

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26147: ------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.0.AM1) > Incremental publish not working with WF13, WF12 and WF11 > -------------------------------------------------------- > > Key: JBIDE-26147 > URL: https://issues.jboss.org/browse/JBIDE-26147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Fix For: 4.9.0.AM2 > > Attachments: helloworld-rs.zip > > > Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context. > This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0. > Then this code is commented out, the application is incrementally published but the error persists -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26147) Incremental publish not working with WF13, WF12 and WF11

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26147: ------------------------------- Sprint: devex #153 August 2019 > Incremental publish not working with WF13, WF12 and WF11 > -------------------------------------------------------- > > Key: JBIDE-26147 > URL: https://issues.jboss.org/browse/JBIDE-26147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Fix For: 4.9.0.AM2 > > Attachments: helloworld-rs.zip > > > Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context. > This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0. > Then this code is commented out, the application is incrementally published but the error persists -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26234) Application wizard: "Git repository URL" and "Git Reference" are not validated

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26234?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26234: ------------------------------------- Attachment: deploy-builder-image-build-configuration.png > Application wizard: "Git repository URL" and "Git Reference" are not validated > ------------------------------------------------------------------------------ > > Key: JBIDE-26234 > URL: https://issues.jboss.org/browse/JBIDE-26234 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Andre Dietisheim > Labels: application_wizard, ux > Fix For: 4.9.x > > Attachments: deploy-builder-image-build-configuration.png > > > steps: > # EXEC: launch application wizard and pick a build image > # ASSERT: "Build Configuration" page shows up featuring "Git repository URL" and "Git Reference" text field > !image-2018-07-27-11-37-37-262.png! > # EXE: provide some bogus git url and bogus git reference > # EXE: hit "Finish" > Result: > Resources on OpenShift get created but then the import fails > Expected result: > "Git Repository URL" and "Git Reference" fields should be validated before hitting "Finish". One could even lookup the git repository at the given url and find out about the available "Git reference" offering them as a combo-box -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26234) Application wizard: "Git repository URL" and "Git Reference" are not validated

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26234?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26234: ------------------------------------- Description: steps: # EXEC: launch application wizard and pick a build image # ASSERT: "Build Configuration" page shows up featuring "Git repository URL" and "Git Reference" text field !deploy-builder-image-build-configuration.png! # EXE: provide some bogus git url and bogus git reference # EXE: hit "Finish" Result: Resources on OpenShift get created but then the import fails Expected result: "Git Repository URL" and "Git Reference" fields should be validated before hitting "Finish". One could even lookup the git repository at the given url and find out about the available "Git reference" offering them as a combo-box was: steps: # EXEC: launch application wizard and pick a build image # ASSERT: "Build Configuration" page shows up featuring "Git repository URL" and "Git Reference" text field !image-2018-07-27-11-37-37-262.png! # EXE: provide some bogus git url and bogus git reference # EXE: hit "Finish" Result: Resources on OpenShift get created but then the import fails Expected result: "Git Repository URL" and "Git Reference" fields should be validated before hitting "Finish". One could even lookup the git repository at the given url and find out about the available "Git reference" offering them as a combo-box > Application wizard: "Git repository URL" and "Git Reference" are not validated > ------------------------------------------------------------------------------ > > Key: JBIDE-26234 > URL: https://issues.jboss.org/browse/JBIDE-26234 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Andre Dietisheim > Labels: application_wizard, ux > Fix For: 4.9.x > > Attachments: deploy-builder-image-build-configuration.png > > > steps: > # EXEC: launch application wizard and pick a build image > # ASSERT: "Build Configuration" page shows up featuring "Git repository URL" and "Git Reference" text field > !deploy-builder-image-build-configuration.png! > # EXE: provide some bogus git url and bogus git reference > # EXE: hit "Finish" > Result: > Resources on OpenShift get created but then the import fails > Expected result: > "Git Repository URL" and "Git Reference" fields should be validated before hitting "Finish". One could even lookup the git repository at the given url and find out about the available "Git reference" offering them as a combo-box -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 July 2018