January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24880) deprecate SOAP from jbosstools-webservices

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24880?page=com.atlassian.jira.plugi... ] Bob Davis commented on JBIDE-24880: ----------------------------------- Will splitting it out give us any metrics on usage? I'd be reluctant to remove it if people are using it. What's the workload involved in leaving things as-is? Bob > deprecate SOAP from jbosstools-webservices > ------------------------------------------ > > Key: JBIDE-24880 > URL: https://issues.jboss.org/browse/JBIDE-24880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, webservices > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.x > > Attachments: Screenshot from 2018-01-23 14-37-52.png > > > [~psrna] suggests we deprecate the SOAP stuff in Webservices. > I'll let him explain which feature(s) are included in this suggestion. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Bob Davis commented on JBIDE-25455: ----------------------------------- Sorry for the late reply - but yeah, it can be removed. Thanks - Bob > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Labels: releasework > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png, remove-buildship-from-jbt-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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: ------------------------------------------ [~jeffmaury] could be an change that we missed in minishift versions. I switched back to cdk-320 when I faced the springboot permission problems. Online is running an OpenShift version that's matching the cdk in version 3.3.0. Testing it. > 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, 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-571) 528414 – Launcher segfault under Wayland when openFile is used

by Leo Ufimtsev (JIRA)

[ https://issues.jboss.org/browse/ERT-571?page=com.atlassian.jira.plugin.sy... ] Leo Ufimtsev closed ERT-571. ---------------------------- Resolution: Done > 528414 – Launcher segfault under Wayland when openFile is used > -------------------------------------------------------------- > > Key: ERT-571 > URL: https://issues.jboss.org/browse/ERT-571 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Leo Ufimtsev > Assignee: Leo Ufimtsev > Labels: SWT > Original Estimate: 3 weeks > Time Spent: 1 week, 2 days, 4 hours > Remaining Estimate: 1 week, 2 days, 4 hours > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-574) Stage 2: Implement mechanism to open in last focused instance.

by Leo Ufimtsev (JIRA)

[ https://issues.jboss.org/browse/ERT-574?page=com.atlassian.jira.plugin.sy... ] Leo Ufimtsev resolved ERT-574. ------------------------------ Resolution: Done > Stage 2: Implement mechanism to open in last focused instance. > -------------------------------------------------------------- > > Key: ERT-574 > URL: https://issues.jboss.org/browse/ERT-574 > Project: Eclipse Release Train > Issue Type: Sub-task > Reporter: Leo Ufimtsev > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25664) Sunsetting download manager jboss.org accounts

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25664?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25664: -------------------------------- Sprint: devex #145 February 2018 > Sunsetting download manager jboss.org accounts > ---------------------------------------------- > > Key: JBIDE-25664 > URL: https://issues.jboss.org/browse/JBIDE-25664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.5.3.AM1 > Reporter: Rob Stryker > Fix For: 4.5.3.AM1 > > > jboss.org accounts will be deprecated for downloadmanager. > See email thread for more information, or, add more information here as it becomes available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25664) Sunsetting download manager jboss.org accounts

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25664?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25664: -------------------------------- Fix Version/s: 4.5.3.AM1 > Sunsetting download manager jboss.org accounts > ---------------------------------------------- > > Key: JBIDE-25664 > URL: https://issues.jboss.org/browse/JBIDE-25664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.5.3.AM1 > Reporter: Rob Stryker > Fix For: 4.5.3.AM1 > > > jboss.org accounts will be deprecated for downloadmanager. > See email thread for more information, or, add more information here as it becomes available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25664) Sunsetting download manager jboss.org accounts

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25664?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-25664: ----------------------------------- Assignee: Rob Stryker > Sunsetting download manager jboss.org accounts > ---------------------------------------------- > > Key: JBIDE-25664 > URL: https://issues.jboss.org/browse/JBIDE-25664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.5.3.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > jboss.org accounts will be deprecated for downloadmanager. > See email thread for more information, or, add more information here as it becomes available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25664) Sunsetting download manager jboss.org accounts

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-25664: ----------------------------------- Summary: Sunsetting download manager jboss.org accounts Key: JBIDE-25664 URL: https://issues.jboss.org/browse/JBIDE-25664 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.5.3.AM1 Reporter: Rob Stryker jboss.org accounts will be deprecated for downloadmanager. See email thread for more information, or, add more information here as it becomes available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25611: ------------------------------------ Just created the node sample on CDK. Did not see the debug port in the deployment config > 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, 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)

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