August 2018 - jbosstools-issues - Jboss List Archives

[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 2018, devex #154 September 2018 (was: devex #153 August 2018) > 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.x > > 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, 2 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 2018, devex #154 September 2018 (was: devex #153 August 2018) > 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.x > > > Implements a Launcher based project wizard using the implemented model -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 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: ------------------------------- Sprint: devex #150 June 2018, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018 (was: devex #150 June 2018, devex #152 July 2018, devex #153 August 2018) > 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: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.x > > Attachments: image-2018-06-22-19-02-57-247.png > > > 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 > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25000: ------------------------------- Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018) > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.png! > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26151) When creating a resource label, rule must be displayed first

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26151?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26151: ------------------------------- Sprint: devex #152 July 2018, devex #153 August 2018, devex #154 September 2018 (was: devex #152 July 2018, devex #153 August 2018) > When creating a resource label, rule must be displayed first > ------------------------------------------------------------ > > Key: JBIDE-26151 > URL: https://issues.jboss.org/browse/JBIDE-26151 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.9.x > > > When creating a resource label, rule apply to label value. It is displayed only if user enters a wrong value. It would be better to display the rule when the wizard is displayed. > See https://redhat.invisionapp.com/share/5YJVZE7PJNX#/screens/298377516 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26230) Implement Tycho build

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26230?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26230: ------------------------------- Sprint: devex #153 August 2018, devex #154 September 2018 (was: devex #153 August 2018) > Implement Tycho build > --------------------- > > Key: JBIDE-26230 > URL: https://issues.jboss.org/browse/JBIDE-26230 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.9.x > > > Switch the Maven build to Tycho for: > * centralized management of dependencies > * unit tests in OSGI env -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26232) Implement CDK support

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26232?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26232: ------------------------------- Sprint: devex #153 August 2018, devex #154 September 2018 (was: devex #153 August 2018) > Implement CDK support > --------------------- > > Key: JBIDE-26232 > URL: https://issues.jboss.org/browse/JBIDE-26232 > 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 > > > In addition to upstream CDK, we should support Red Hat CDK supports in RST as well -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26236) Create New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26236?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26236. ------------------------------ Resolution: Done > Create New and Noteworthy for 4.9.0.AM2 > --------------------------------------- > > Key: JBIDE-26236 > URL: https://issues.jboss.org/browse/JBIDE-26236 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.9.0.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26249) OpenShift New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26249?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26249: ------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.0.AM3) > OpenShift New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26249 > URL: https://issues.jboss.org/browse/JBIDE-26249 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for OpenShift 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26249) OpenShift New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26249?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26249: ---------------------------------- Assignee: Jeff MAURY (was: Andre Dietisheim) > OpenShift New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26249 > URL: https://issues.jboss.org/browse/JBIDE-26249 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for OpenShift 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018