[JBoss JIRA] (JBIDE-26072) Manage Projects wizard: project that I deleted is still listed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26072?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26072:
-------------------------------------
Attachment: marked-for-deletion.png
> Manage Projects wizard: project that I deleted is still listed
> --------------------------------------------------------------
>
> Key: JBIDE-26072
> URL: https://issues.jboss.org/browse/JBIDE-26072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Labels: manage_projects_wizard
> Fix For: 4.6.x
>
> Attachments: image-2018-06-01-16-08-59-257.png, marked-for-deletion.png
>
>
> steps:
> # ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
> # ASSERT: have at least 1 project in your OpenShift
> # EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
> # ASSERT: "Manage Projects" wizard shows up, listing all projects
> # EXEC: select 1 project and hit "Remove..."
> # EXEC: when asked to confirm the removal, hit "OK"
> # ASSERT: wizard gets disabled, progress bar shows up telling you that your project is being deleted.
> Result:
> Once the progressbar is gone and all the wizard is enabled again, the project is still listed
> !image-2018-06-01-16-08-59-257.png!
> Workaround: hit "Refresh..."
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26072) Manage Projects wizard: project that I deleted is still listed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26072?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26072:
------------------------------------------
JBIDE-26092 suggest using markers (decorator icon in the name column? displaying the name italic and adding "(maked for deletion...)"? tooltip?)
See how the web-ui does it with a decorator icon and a tooltip:
!marked-for-deletion.png!
> Manage Projects wizard: project that I deleted is still listed
> --------------------------------------------------------------
>
> Key: JBIDE-26072
> URL: https://issues.jboss.org/browse/JBIDE-26072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Labels: manage_projects_wizard
> Fix For: 4.6.x
>
> Attachments: image-2018-06-01-16-08-59-257.png, marked-for-deletion.png
>
>
> steps:
> # ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
> # ASSERT: have at least 1 project in your OpenShift
> # EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
> # ASSERT: "Manage Projects" wizard shows up, listing all projects
> # EXEC: select 1 project and hit "Remove..."
> # EXEC: when asked to confirm the removal, hit "OK"
> # ASSERT: wizard gets disabled, progress bar shows up telling you that your project is being deleted.
> Result:
> Once the progressbar is gone and all the wizard is enabled again, the project is still listed
> !image-2018-06-01-16-08-59-257.png!
> Workaround: hit "Refresh..."
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26092) Add marker for projects marked for deletion
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26092?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26092:
------------------------------------------
[~jkopriva] +1, that's exactly what I was complaining about in JBIDE-26072. My suggestion was to provide a "status" column, a marker would be grasped even more quickly.
> Add marker for projects marked for deletion
> -------------------------------------------
>
> Key: JBIDE-26092
> URL: https://issues.jboss.org/browse/JBIDE-26092
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Environment: https://console.engint.openshift.com
> Reporter: Josef Kopriva
> Attachments: image-2018-06-12-12-52-05-930.png
>
>
> I have created several projects on https://console.engint.openshift.com instance, but I have deleted these projects afterwards. If I try to delete them once again an error message shows up:
> !image-2018-06-12-12-52-05-930.png|thumbnail!
> User should be informed about status of these projects before deleting them once again with icon or something.
> Steps to reproduce:
> 1. Create connection to https://console.engint.openshift.com
> 2. Create several projects with applications in this connection
> 3. Delete these projects
> 4. After refresh some projects shows up
> 5. When you try to delete them once again an error shows up
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22138:
------------------------------------------
[~ksuzumur] ok, np, thanks for providing the info.
Can you tell us a bit more on how the client using the OpenShift Eclipse tooling? We'd very much appreciate such insights so that we can match the users expectations to the tooling.
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.x
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22138:
-------------------------------------
Description:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
steps:
# EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
# EXEC: import the app into your Eclipse workspace
# EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
# EXEC: create a server adapter and start it
# ASSERT: adapter starts syncing, verify what war is used
Result:
The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
was:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.x
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4706:
-----------------------------
Attachment: devstudio12-central.png
> Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4706
> URL: https://issues.jboss.org/browse/JBDS-4706
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.0.0.AM3
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico
>
>
> Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio".
> We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4706:
----------------------------------
New screenshot of RH Central in devstudio:
!devstudio12-central.png|thumbnail!
> Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4706
> URL: https://issues.jboss.org/browse/JBDS-4706
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.0.0.AM3
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico
>
>
> Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio".
> We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months