March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23490: ------------------------------------------ cherry-picked into jbosstools-4.4.x and bumped openshift.js and openshift.js.feature, there, too > Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23490 > URL: https://issues.jboss.org/browse/JBIDE-23490 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > Attachments: ScaledUpPodProblems.webm > > > When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application. > The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24044) Upgrade Forge Runtime to 3.6.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24044?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-24044: ------------------------------------ Fix Version/s: 4.5.0.AM1 > Upgrade Forge Runtime to 3.6.0.Final > ------------------------------------ > > Key: JBIDE-24044 > URL: https://issues.jboss.org/browse/JBIDE-24044 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.3.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24044) Upgrade Forge Runtime to 3.6.0.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-24044: --------------------------------------- Summary: Upgrade Forge Runtime to 3.6.0.Final Key: JBIDE-24044 URL: https://issues.jboss.org/browse/JBIDE-24044 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.4.3.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.4.4.AM1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23490: ------------------------------------------ merged PR into master and bumped openshift.js and openshift.js.feature > Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23490 > URL: https://issues.jboss.org/browse/JBIDE-23490 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > Attachments: ScaledUpPodProblems.webm > > > When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application. > The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23490: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1405, https://github.com/jbosstools/jbosstools-openshift/pull/1422, https://github.com/jbosstools/jbosstools-openshift/pull/1427, https://github.com/jbosstools/jbosstools-openshift/pull/1443 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1405, https://github.com/jbosstools/jbosstools-openshift/pull/1422, https://github.com/jbosstools/jbosstools-openshift/pull/1427) > Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23490 > URL: https://issues.jboss.org/browse/JBIDE-23490 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > Attachments: ScaledUpPodProblems.webm > > > When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application. > The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24043) Upversion jbosstools-server in master and maintenance

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-24043: ----------------------------------- Summary: Upversion jbosstools-server in master and maintenance Key: JBIDE-24043 URL: https://issues.jboss.org/browse/JBIDE-24043 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.4.AM1, 4.5.0.AM1 Reporter: Rob Stryker In maintenance: archives from 3.6.103 to 3.6.104 jmx from 1.8.3 to 1.9.0 bc of API change wtp from 1.3.103 to 1.3.104 AS from 3.2.3 to 3.2.4 In Master archives from 3.6.103 to 3.6.110 to leave room in case of emergency jmx from 1.8.3 to 1.10.0 to leave room and also bc I expect further changes wtp from 1.3.103 to 1.3.110 to leave room in case of emergency AS from 3.2.3 to 3.3.0 because I expect API additions and new features -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24029) Create JMX Connection wizard can not be finished when Jolokia plugin is activated

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24029?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-24029 at 3/8/17 12:27 PM: -------------------------------------------------------------- pushed to master and maintenance was (Author: rob.stryker): pushed to master > Create JMX Connection wizard can not be finished when Jolokia plugin is activated > --------------------------------------------------------------------------------- > > Key: JBIDE-24029 > URL: https://issues.jboss.org/browse/JBIDE-24029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.2.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.4.AM1 > > > - it is working if the jolokia plugin is not installed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23709) Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23709?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23709: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.5.0.AM1) > Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23709 > URL: https://issues.jboss.org/browse/JBIDE-23709 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Fix For: 4.4.4.AM2 > > Attachments: project-selected-no-scaling.png, service-selected-scaling-possible.png > > > steps to reproduce: > # ASSERT: make sure that you have at least 1 service & pod running in OpenShift > # EXEC: in OpenShift Explorer: select the project that contains the service/pod > # EXEC: in Properties view: select "Pod" tab and then your running pod (not the build pod, but the pod that's running your service). Open up the context menu > Result: > "Scale" with is child entries is missing from the context menu. > !project-selected-no-scaling.png! > While it's present if you have the service selected in the OpenShift Explorer. > !service-selected-scaling-possible.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23893) [cdk] follow up on changes to cdk3 for marker file

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23893?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23893: ------------------------------------- The problem here is that the runtime detection API is very much filesystem / folder oriented. You pick a folder and it scans deep, and asks each runtime detector to 'find' a runtime in each folder. So the driver is the filesystem tree, and then it asks the rt detectors. It doesn't stop when it finds one runtime. It will keep scanning for others. This will become very inefficient if it still tries to scan the entire fs or folder structure of a user's home directory. But to reverse the logic would be a huge API change. > [cdk] follow up on changes to cdk3 for marker file > -------------------------------------------------- > > Key: JBIDE-23893 > URL: https://issues.jboss.org/browse/JBIDE-23893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.3.Final > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.4.4.AM2 > > > cdk v3 added marker files with credentials and version information. We need to make use of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23784) WF 11 / EAP 7.1 Incremental MGMT publishing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23784?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23784: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.4.AM1) > WF 11 / EAP 7.1 Incremental MGMT publishing > ------------------------------------------- > > Key: JBIDE-23784 > URL: https://issues.jboss.org/browse/JBIDE-23784 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM2 > > > WF 11 and EAP 7.1 will have support for management deployment in an incremental fashion. > WF 11 nightly builds for the pre-alpha are here: https://developer.jboss.org/thread/224262 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017