January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25587) Running EAP 7.1 server is not selected by default when deploying

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25587?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25587: -------------------------------- Attachment: JBIDE-25587.ogv > Running EAP 7.1 server is not selected by default when deploying > ---------------------------------------------------------------- > > Key: JBIDE-25587 > URL: https://issues.jboss.org/browse/JBIDE-25587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.2.Final > Environment: FC27 > Red Hat JBoss Developer Studio > Version: 11.2.0.GA > Build id: GA-v20180115-0516-B1866 > Build date: 20180115-0516 > EAP 7.1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Attachments: JBIDE-25587.ogv, image-2018-01-16-13-42-38-197.png > > > Please make default selection on running server in *Run On Server* dialog. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25611: ------------------------------------------ there are obviously several problems at play here. Need to isolate them. > Server adapter: timeouts when starting into "Debug" on OpenShift Online > ----------------------------------------------------------------------- > > Key: JBIDE-25611 > URL: https://issues.jboss.org/browse/JBIDE-25611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.3.AM1 > > Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, image-2018-01-26-00-49-39-691.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png > > > # ASSERT: have an account on OpenShift Online > # EXEC: create a new application via template nodejs-mongo-persistent > # EXEC: have the project imported into the workspace and the server adapter for it created > # ASSERT: you have a new server adapter for your app in state [stopped] > # EXEC: start the adapter into "Debug" > Result: > The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog: > !error-waiting-for-new-pod.png! > In the Eclipse log you'll find the following: > {code} > org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170) > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25620) Hibernate New and Noteworthy for 4.5.3.AM1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25620?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-25620. ----------------------------- Resolution: Rejected > Hibernate New and Noteworthy for 4.5.3.AM1 > --------------------------------------------------- > > Key: JBIDE-25620 > URL: https://issues.jboss.org/browse/JBIDE-25620 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Labels: task > Fix For: 4.5.3.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-25618 #comment Create N&N for Hibernate 4.5.3.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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-13407: ----------------------------------------- I attended a conference last 2 days and they mentioned 2 times the usage of [HashiCorp Vault|https://www.vaultproject.io/] to manage secrets and jar signing with GPG key. Some parts are fairly new. Maybe there are new shiny stuff that can be used. > Jar signing for JBT plugins/features > ------------------------------------ > > Key: JBIDE-13407 > URL: https://issues.jboss.org/browse/JBIDE-13407 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png > > > Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product. > Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25000 at 1/26/18 12:52 PM: -------------------------------------------------------------------- I can reproduce this on our internal instance at https://open.pass.openshift.com was (Author: adietish): I can reproduce this on our internal instance at *https://open.pass.openshift*.com > 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.5.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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25668) Properties view displays a strange label for OpenShift3 connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25668?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25668: ------------------------------- Description: When an OpenShift3 connection is displayed, the Properties view displays a strange labelled property called Org.jbosstools.openshift.core.connection.ext.oc.location (was: When an OpenShit3 connection is displayed, the Properties view displays a strange labelled property called Org.jbosstools.openshift.core.connection.ext.oc.location) > Properties view displays a strange label for OpenShift3 connections > ------------------------------------------------------------------- > > Key: JBIDE-25668 > URL: https://issues.jboss.org/browse/JBIDE-25668 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3, properties > Fix For: 4.5.x > > Attachments: screenshot-1.png > > > When an OpenShift3 connection is displayed, the Properties view displays a strange labelled property called Org.jbosstools.openshift.core.connection.ext.oc.location -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25668) Properties view displays a strange label for OpenShift3 connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25668?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25668: ------------------------------- Attachment: screenshot-1.png > Properties view displays a strange label for OpenShift3 connections > ------------------------------------------------------------------- > > Key: JBIDE-25668 > URL: https://issues.jboss.org/browse/JBIDE-25668 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3, properties > Fix For: 4.5.x > > Attachments: screenshot-1.png > > > When an OpenShit3 connection is displayed, the Properties view displays a strange labelled property called Org.jbosstools.openshift.core.connection.ext.oc.location -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25668) Properties view displays a strange label for OpenShift3 connections

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-25668: ---------------------------------- Summary: Properties view displays a strange label for OpenShift3 connections Key: JBIDE-25668 URL: https://issues.jboss.org/browse/JBIDE-25668 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.2.Final Reporter: Jeff MAURY Fix For: 4.5.x When an OpenShit3 connection is displayed, the Properties view displays a strange labelled property called Org.jbosstools.openshift.core.connection.ext.oc.location -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25667) Add itests for CDK server adapter for Minishift binary

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25667?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25667: ---------------------------------- Issue Type: Feature Request (was: Enhancement) > Add itests for CDK server adapter for Minishift binary > ------------------------------------------------------ > > Key: JBIDE-25667 > URL: https://issues.jboss.org/browse/JBIDE-25667 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, integration-tests > Affects Versions: 4.5.3.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25667) Add itests for Minishift server adapter

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25667?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25667: ---------------------------------- Summary: Add itests for Minishift server adapter (was: Add itests for CDK server adapter for Minishift binary) > Add itests for Minishift server adapter > --------------------------------------- > > Key: JBIDE-25667 > URL: https://issues.jboss.org/browse/JBIDE-25667 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, integration-tests > Affects Versions: 4.5.3.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

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 January 2018