June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Attachment: edit-connection-4.png > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png, edit-connection-4.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have a valid username/pw v3 connection listed in explorer # EXEC: in OpenShift explorer: pick "Edit Connection" in the context-menu of your connection # ASSERT: connection wizard pops up with your selected connection. It defaults to OAuth though. !edit-connection-1.png! # EXEC: Switch Protocol from OAuth to Basic and provide some username that differs from what you know it was set to when it worked. Provide password (ex. test-admin->adietish) !edit-connection-2.png! # EXEC: hit "Finish" # ASSERT: authentication worked, the connection dialog is closed Result: In explorer you still have the old username displayed (ex. test-admin). EXEC: in Explorer: pick "Refresh" in the context-menu of your connection Result: No change, the connection still lists the projects and displays the old username !edit-connection-3.png! EXEC: close OpenShift Explorer and open it again Result: The connection now shows up with the changed username !edit-connection-4.png! was: # ASSERT: make sure that you have a valid username/pw v3 connection listed in explorer # EXEC: in OpenShift explorer: pick "Edit Connection" in the context-menu of your connection # ASSERT: connection wizard pops up with your selected connection. It defaults to OAuth though. !edit-connection-1.png! # EXEC: Switch Protocol from OAuth to Basic and provide some username that differs from what you know it was set to when it worked. Provide password (ex. test-admin->adietish) !edit-connection-2.png! # EXEC: hit "Finish" # ASSERT: authentication worked, the connection dialog is closed Result: In explorer you still have the old username displayed (ex. test-admin). EXEC: in Explorer: pick "Refresh" in the context-menu of your connection Result: No change, the connection still lists the projects and displays the old username !edit-connection-3.png! EXEC: close OpenShift Explorer and open it again Result: The connection now shows up with the changed username > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png, edit-connection-4.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on JBIDE-19641: ------------------------------------------ Just an FYI, I mentioned on the mail thread that the code path for the CLI and what JBIDE is using is the same once it reaches the point where the bits are being pushed to the server (which is where things are stuck.) But it turns out that's not the case; the management op the CLI uses is different. > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have a valid username/pw v3 connection listed in explorer # EXEC: in OpenShift explorer: pick "Edit Connection" in the context-menu of your connection # ASSERT: connection wizard pops up with your selected connection. It defaults to OAuth though. !edit-connection-1.png! # EXEC: Switch Protocol from OAuth to Basic and provide some username that differs from what you know it was set to when it worked. Provide password (ex. test-admin->adietish) !edit-connection-2.png! # EXEC: hit "Finish" # ASSERT: authentication worked, the connection dialog is closed Result: In explorer you still have the old username displayed (ex. test-admin). EXEC: in Explorer: pick "Refresh" in the context-menu of your connection Result: No change, the connection still lists the projects and displays the old username !edit-connection-3.png! EXEC: close OpenShift Explorer and open it again Result: The connection now shows up with the changed username was: # ASSERT: make sure that you have a valid username/pw v3 connection listed in explorer # EXEC: in OpenShift explorer: pick "Edit Connection" in the context-menu of your connection # ASSERT: connection wizard pops up with your selected connection. It defaults to OAuth though. !edit-connection-1.png! # EXEC: Switch Protocol from OAuth to Basic and provide some username that differs from what you know it was set to when it worked. Provide password (ex. test-admin->adietish) !edit-connection-2.png! # EXEC: hit "Finish" # ASSERT: authentication worked, the connection dialog is closed Result: In explorer you still have the old username displayed (ex. test-admin). EXEC: in Explorer: pick "Refresh" in the context-menu of your connection Result: No change, the connection still lists the projects and displays the old username !edit-connection-3.png! > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18772: --------------------------------------- [~mickael_istria] integration tests build now works, thanks for that: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... But isn't what you did in https://github.com/jbosstools/jbosstools-integration-tests/pull/990 basically copying the whole profile? Integration tests inherit the parent pom, whereas RedDeer doesn't. Does RedDeer need anything more than what you did for integration tests? > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have a valid username/pw v3 connection listed in explorer # EXEC: in OpenShift explorer: pick "Edit Connection" in the context-menu of your connection # ASSERT: connection wizard pops up with your selected connection. It defaults to OAuth though. !edit-connection-1.png! # EXEC: Switch Protocol from OAuth to Basic and provide some username that differs from what you know it was set to when it worked. Provide password (ex. test-admin->adietish) !edit-connection-2.png! # EXEC: hit "Finish" # ASSERT: authentication worked, the connection dialog is closed Result: In explorer you still have the old username displayed (ex. test-admin). EXEC: in Explorer: pick "Refresh" in the context-menu of your connection Result: No change, the connection still lists the projects and displays the old username !edit-connection-3.png! was: # ASSERT: make sure that you have a valid username/pw v3 connection listed in explorer # EXEC: in OpenShift explorer: pick "Edit Connection" in the context-menu of your connection # ASSERT: connection wizard pops up with your selected connection. It defaults to OAuth though. !!edit-resources-1.png! # EXEC: Switch Protocol from OAuth to Basic and provide some username that differs from what you know it was set to when it worked. Provide password (ex. test-admin->adietish) !edit-resources-2.png! # EXEC: hit "Finish" # ASSERT: authentication worked, the connection dialog is closed Result: In explorer you still have the old username displayed (ex. test-admin). EXEC: in Explorer: pick "Refresh" in the context-menu of your connection Result: No change, the connection still lists the projects and displays the old username !edit-resources-3.png! > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19909?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19909: ------------------------------------- Attachment: edit-connection-1.png edit-connection-2.png edit-connection-3.png > Connection wizard: Changing username has no visible effect, refresh doesnt help > ------------------------------------------------------------------------------- > > Key: JBIDE-19909 > URL: https://issues.jboss.org/browse/JBIDE-19909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Attachments: edit-connection-1.png, edit-connection-2.png, edit-connection-3.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19909) Connection wizard: Changing username has no visible effect, refresh doesnt help

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19909: ---------------------------------------- Summary: Connection wizard: Changing username has no visible effect, refresh doesnt help Key: JBIDE-19909 URL: https://issues.jboss.org/browse/JBIDE-19909 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Jeff Cantrill -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19848) Include Eclipse Docker Tooling in the Target Platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19848?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19848: ----------------------------------- Description: *Reason:* Include Eclipse Docker Tooling in JBoss Tools and Dev Studio *Project page/sources:* http://eclipse.org/linuxtools *Version:* 4.0.0 *License and owner:* EPL *Original p2 repo:* http://download.eclipse.org/linuxtools/updates-docker-nightly/ *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/docker/1.0.0.20... (from https://github.com/jbosstools/jbosstools-download.jboss.org/pull/526 ) *Include Sources:* Yes *Affected projects:* Docker tooling should be installable from JBoss Tools update site and should be part of DevStudio *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} see https://github.com/jbosstools/jbosstools-target-platforms/pull/149 {code} was: *Reason:* Include Eclipse Docker Tooling in JBoss Tools and Dev Studio *Project page/sources:* http://eclipse.org/linuxtools *Version:* 4.0.0 *License and owner:* EPL *Original p2 repo:* http://download.eclipse.org/linuxtools/updates-docker-nightly/ *JBoss mirror:* see https://github.com/jbosstools/jbosstools-download.jboss.org/pull/526 *Include Sources:* Yes *Affected projects:* Docker tooling should be installable from JBoss Tools update site and should be part of DevStudio *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} see https://github.com/jbosstools/jbosstools-target-platforms/pull/149 {code} > Include Eclipse Docker Tooling in the Target Platforms > ------------------------------------------------------ > > Key: JBIDE-19848 > URL: https://issues.jboss.org/browse/JBIDE-19848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, target-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > *Reason:* Include Eclipse Docker Tooling in JBoss Tools and Dev Studio > *Project page/sources:* http://eclipse.org/linuxtools > *Version:* 4.0.0 > *License and owner:* EPL > *Original p2 repo:* http://download.eclipse.org/linuxtools/updates-docker-nightly/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/docker/1.0.0.20... (from https://github.com/jbosstools/jbosstools-download.jboss.org/pull/526 ) > *Include Sources:* Yes > *Affected projects:* Docker tooling should be installable from JBoss Tools update site and should be part of DevStudio > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > see https://github.com/jbosstools/jbosstools-target-platforms/pull/149 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19848) Include Eclipse Docker Tooling in the Target Platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19848?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19848: ---------------------------------------- Mirror created at http://download.jboss.org/jbosstools/updates/requirements/docker/1.0.0.20... > Include Eclipse Docker Tooling in the Target Platforms > ------------------------------------------------------ > > Key: JBIDE-19848 > URL: https://issues.jboss.org/browse/JBIDE-19848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, target-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > *Reason:* Include Eclipse Docker Tooling in JBoss Tools and Dev Studio > *Project page/sources:* http://eclipse.org/linuxtools > *Version:* 4.0.0 > *License and owner:* EPL > *Original p2 repo:* http://download.eclipse.org/linuxtools/updates-docker-nightly/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/docker/1.0.0.20... (from https://github.com/jbosstools/jbosstools-download.jboss.org/pull/526 ) > *Include Sources:* Yes > *Affected projects:* Docker tooling should be installable from JBoss Tools update site and should be part of DevStudio > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > see https://github.com/jbosstools/jbosstools-target-platforms/pull/149 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015