August 2018 - jbosstools-issues - Jboss List Archives

[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 (was: devex #150 June 2018, devex #152 July 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.0.AM2 > > 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, 8 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 (was: devex #138 September 2017, devex #152 July 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4710: ----------------------------- Sprint: devex #152 July 2018, devex #153 August 2018 (was: devex #152 July 2018) > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.9.0.AM1 > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26175: ------------------------------- Sprint: devex #152 July 2018, devex #153 August 2018 (was: devex #152 July 2018) > Cannot create server adapter for eap71-basic-s2i template from CDK > ------------------------------------------------------------------ > > Key: JBIDE-26175 > URL: https://issues.jboss.org/browse/JBIDE-26175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.6.0.Final > Environment: CDK: CDK v3.5.0-1 > Red Hat Developer Studio > Version: 12.0.0.GA > Build id: GA-v20180706-1014-B2970 > OS: Linux, v.4.17.3-200.fc28.x86_64, x86_64 / gtk 3.22.30, WebKit 2.20.3 > Java version: 1.8.0_172 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: regression, upstream > Fix For: 4.9.0.AM1 > > > I was not able to create server adapter for eap71-basic-s2i template application. > Pod error log: > {code:java} > --> Scaling eap-app-1 down to zero > --> Scaling eap-app-2 to 1 before performing acceptance check > error: update acceptor rejected eap-app-2: pods for rc 'myproject/eap-app-2' took longer than 600 seconds to become available > {code} > Error log from OpenShift console: > {code:java} > Readiness probe failed: { > "probe.eap.dmr.EapProbe": { > "probe.eap.dmr.ServerStatusTest": "running", > "probe.eap.dmr.DeploymentTest": "Exception executing test: unorderable types: Status() < Status()", > "probe.eap.dmr.BootErrorsTest": [ > { > "failed-operation": { > "operation": "deploy", > "address": [ > { > "deployment": "kitchensink.war" > } > ] > }, > "failure-description": "{\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"kitchensink.war\\\".FIRST_MODULE_USE\" => \"WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \\\"kitchensink.war\\\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\\\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\\\".statistics is already registered\"}}", > "failed-services": { > "jboss.deployment.unit.\"kitchensink.war\".FIRST_MODULE_USE": "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"kitchensink.war\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered" > } > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 (was: devex #152 July 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26206) Create New and Noteworthy for 4.9.0.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26206?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26206. ------------------------------ Resolution: Done > Create New and Noteworthy for 4.9.0.AM1 > --------------------------------------- > > Key: JBIDE-26206 > URL: https://issues.jboss.org/browse/JBIDE-26206 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.9.0.AM1 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26210) Hibernate New and Noteworthy for 4.9.0.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26210?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26210. ------------------------------ Resolution: Done > Hibernate New and Noteworthy for 4.9.0.AM1 > --------------------------------------------------- > > Key: JBIDE-26210 > URL: https://issues.jboss.org/browse/JBIDE-26210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM1 > > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate 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 Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate 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-26206 #comment Create N&N for Hibernate 4.9.0.AM1 #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 Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-26278: ------------------------------- Story Points: 13 > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.0.AM2 > > > TBD -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26210) Hibernate New and Noteworthy for 4.9.0.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26210?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26210: ---------------------------------- Assignee: Jeff MAURY (was: Koen Aers) > Hibernate New and Noteworthy for 4.9.0.AM1 > --------------------------------------------------- > > Key: JBIDE-26210 > URL: https://issues.jboss.org/browse/JBIDE-26210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM1 > > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate 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 Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate 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-26206 #comment Create N&N for Hibernate 4.9.0.AM1 #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 Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26279) Fix failing jax-rs itests

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-26279: ---------------------------------- Summary: Fix failing jax-rs itests Key: JBIDE-26279 URL: https://issues.jboss.org/browse/JBIDE-26279 Project: Tools (JBoss Tools) Issue Type: Task Components: webservices Reporter: Pavol Srna Assignee: Pavol Srna Fix For: 4.9.0.AM2 TBD -- 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 August 2018