March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16921) Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16921?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-16921. -------------------------------------- Assignee: Andre Dietisheim Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16921 > URL: https://issues.jboss.org/browse/JBIDE-16921 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > > ASSERT: Have a connection (e.g. seconduser(a)somewhere.xx) in OpenShift Explorer. > EXEC: Add another connection starting with a letter that's first in the alphabetical order (there is alphabetical order e.g. firstuser(a)somewhere.xx). It'll be listed first in the Explorer . > EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application. > ASSERT: Wizard is opened. First connection is preselected. > EXEC: close wizard > EXEC: Remove first connection from OpenShift explorer. > EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application > RESULT: Connection dialog is show with <NEW CONNECTION> preselected > EXPECTED RESULT: Connection dialog is shown with remaining connection preselected -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16921) Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16921?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16921: ------------------------------------- Fix Version/s: 4.5.3.Final (was: LATER) > Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16921 > URL: https://issues.jboss.org/browse/JBIDE-16921 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: application_wizard > Fix For: 4.5.3.Final > > > ASSERT: Have a connection (e.g. seconduser(a)somewhere.xx) in OpenShift Explorer. > EXEC: Add another connection starting with a letter that's first in the alphabetical order (there is alphabetical order e.g. firstuser(a)somewhere.xx). It'll be listed first in the Explorer . > EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application. > ASSERT: Wizard is opened. First connection is preselected. > EXEC: close wizard > EXEC: Remove first connection from OpenShift explorer. > EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application > RESULT: Connection dialog is show with <NEW CONNECTION> preselected > EXPECTED RESULT: Connection dialog is shown with remaining connection preselected -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16879) Explorer: context menu for cartridges opens away from cartridge

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16879?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-16879. -------------------------------------- Assignee: Andre Dietisheim (was: Jeff MAURY) Resolution: Done upstream issue was resolved. Resolving as DONE > Explorer: context menu for cartridges opens away from cartridge > --------------------------------------------------------------- > > Key: JBIDE-16879 > URL: https://issues.jboss.org/browse/JBIDE-16879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) GTK3 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Priority: Minor > Labels: explorer, gtk3, openshift_v2, openshift_v3, upstream > Fix For: 4.5.3.Final > > Attachments: OpenShift_conmenu.png > > > In OpenShift Explorer view, expand tree down to cartridge level for an app. Right-click cartridge. The context menu opens away from mouse pointer rather than adjacent to it as it does for other tree items, like connection, domain or app. > I can 100% of time reproduce it by first right-clicking app and then immediately right-clicking (twice) cartridge. > I can't reproduce it by first right-clicking connection or domain and then immediately right-clicking (twice) cartridge. > !OpenShift_conmenu.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16879) Explorer: context menu for cartridges opens away from cartridge

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16879?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16879: ------------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) > Explorer: context menu for cartridges opens away from cartridge > --------------------------------------------------------------- > > Key: JBIDE-16879 > URL: https://issues.jboss.org/browse/JBIDE-16879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) GTK3 > Reporter: Michelle Murray > Assignee: Jeff MAURY > Priority: Minor > Labels: explorer, gtk3, openshift_v2, openshift_v3, upstream > Fix For: 4.5.3.Final > > Attachments: OpenShift_conmenu.png > > > In OpenShift Explorer view, expand tree down to cartridge level for an app. Right-click cartridge. The context menu opens away from mouse pointer rather than adjacent to it as it does for other tree items, like connection, domain or app. > I can 100% of time reproduce it by first right-clicking app and then immediately right-clicking (twice) cartridge. > I can't reproduce it by first right-clicking connection or domain and then immediately right-clicking (twice) cartridge. > !OpenShift_conmenu.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14890: ------------------------------------- Labels: application_wizard openshift_v2 (was: application_wizard) > Application wizard: Use EGit recursive merge instead of copying git repository > ------------------------------------------------------------------------------ > > Key: JBIDE-14890 > URL: https://issues.jboss.org/browse/JBIDE-14890 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2, 4.1.1.Final > Reporter: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > Attachments: user-existing-project.png > > > OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing") > !user-existing-project.png! > When using the git command line one is told to merge by using the recursive merge startegy: > {code} > git merge -s recursive -X ours foo > {code} > When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over. > EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-14890. -------------------------------------- Fix Version/s: 4.5.3.Final (was: LATER) Assignee: Andre Dietisheim Resolution: Done Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > Application wizard: Use EGit recursive merge instead of copying git repository > ------------------------------------------------------------------------------ > > Key: JBIDE-14890 > URL: https://issues.jboss.org/browse/JBIDE-14890 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2, 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > Attachments: user-existing-project.png > > > OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing") > !user-existing-project.png! > When using the git command line one is told to merge by using the recursive merge startegy: > {code} > git merge -s recursive -X ours foo > {code} > When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over. > EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-14890. -------------------------------------- Resolution: Won't Fix > Application wizard: Use EGit recursive merge instead of copying git repository > ------------------------------------------------------------------------------ > > Key: JBIDE-14890 > URL: https://issues.jboss.org/browse/JBIDE-14890 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2, 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > Attachments: user-existing-project.png > > > OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing") > !user-existing-project.png! > When using the git command line one is told to merge by using the recursive merge startegy: > {code} > git merge -s recursive -X ours foo > {code} > When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over. > EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-14890. ------------------------------------ > Application wizard: Use EGit recursive merge instead of copying git repository > ------------------------------------------------------------------------------ > > Key: JBIDE-14890 > URL: https://issues.jboss.org/browse/JBIDE-14890 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2, 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > Attachments: user-existing-project.png > > > OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing") > !user-existing-project.png! > When using the git command line one is told to merge by using the recursive merge startegy: > {code} > git merge -s recursive -X ours foo > {code} > When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over. > EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13936) Server Adapter: Support deployment on multiple applications (eg: test vs prod)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13936?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-13936. ------------------------------------ > Server Adapter: Support deployment on multiple applications (eg: test vs prod) > ------------------------------------------------------------------------------- > > Key: JBIDE-13936 > URL: https://issues.jboss.org/browse/JBIDE-13936 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final > > > could we support multiple platforms and have a workflow of the following kind: > 1 - user deploys to a 'test' platform/application > 2 - user tests/check it's all good > 3 - if so, he can deploy on the 'production' platform/application > This would mean, for example, having 2 server adapters and being able to support 2 'git remotes' -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13936) Server Adapter: Support deployment on multiple applications (eg: test vs prod)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13936?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13936: ------------------------------------- Fix Version/s: 4.5.3.Final (was: LATER) > Server Adapter: Support deployment on multiple applications (eg: test vs prod) > ------------------------------------------------------------------------------- > > Key: JBIDE-13936 > URL: https://issues.jboss.org/browse/JBIDE-13936 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final > > > could we support multiple platforms and have a workflow of the following kind: > 1 - user deploys to a 'test' platform/application > 2 - user tests/check it's all good > 3 - if so, he can deploy on the 'production' platform/application > This would mean, for example, having 2 server adapters and being able to support 2 'git remotes' -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 March 2018