[
https://issues.jboss.org/browse/JBIDE-17919?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-17919:
-------------------------------------
Steps to Reproduce:
ASSERT: Have a OpenShift application (both in workspace and deployed on a server).
EXEC: Open OpenShift explorer and choose in the context menu of the application Snapshot -
Save...
EXEC: Save a snapshot. It does not matter whether into workspace or somewhere in file
system.
EXEC: Open OpenShift explorer and choose in the context menu of the application Snapshot -
Save...
ASSERT: There is a preselected file name for a snapshot.
EXEC: Switch from Full to Deployment snapshot.
RESULT: File name of a snapshot is still containing keyword full instead of deployment.
EXPECTED RESULT: Snapshot name is changed according to currently selected type.
was:
ASSERT: Have a OpenShift application (both in workspace and deployed on a server).
EXEC: Open OpenShift explorer and choose in the context menu of the application Snapshot -
Save...
ASSERT: There is a preselected file name for a snapshot.
EXEC: Switch from Full to Deployment snapshot.
RESULT: File name of a snapshot is still containing keyword full instead of deployment.
EXPECTED RESULT: Snapshot name is changed according to currently selected type.
Snapshot wizard: snapshot file name is not refreshed upon changes
between full and deployment type
--------------------------------------------------------------------------------------------------
Key: JBIDE-17919
URL:
https://issues.jboss.org/browse/JBIDE-17919
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Beta3
Reporter: Marián Labuda
Assignee: Jeff Cantrill
Labels: snapshot_wizard
Fix For: 4.2.0.CR1
When trying to create a new snapshot of FULL or DEPLOYMENT type after creating a snapshot
earlier, there is no change of file name for the snapshot. It's still the same file
name as it was for the snapshot created right before.
I think there was intention to let user overwrite previously created snapshot. But this
brings complications because of snapshot type. We should not override FULL snapshot with
DEPLOYMENT snapshot. I think also, that there should not be overriding at all, but it
should be distinguished as it is (after workaround) by number of snapshot.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)