[
https://issues.jboss.org/browse/JBIDE-16876?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-16876:
---------------------------------------
[~maxandersen] yeah, that's possible but not in this case. When application is
imported, it is created local git repo and added remote to application git remote repo on
OpenShift. Server adapter is connection between local git repo (imported application) and
remote git repo (deployed application). After using import again, then server adapter
would change target location of local git repo and would not work with original anymore
(or until "assign" this existing server adapter back to the original local git
repo). That mentioned reason was just according to a server adapter - Michelle suggested
to have in context menu of a server adapter items OpenShift - ImportApplication. If users
want to switch workspace etc. they could simply import application (and this import would
create new server adapter between local app and remote app). WDYT?
New Application wizard: page#1 needs fields disabled based on user
actions
--------------------------------------------------------------------------
Key: JBIDE-16876
URL:
https://issues.jboss.org/browse/JBIDE-16876
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Beta1
Reporter: Michelle Murray
Assignee: Andre Dietisheim
Labels: application_wizard
Fix For: 4.2.0.Beta2
Attachments: create-new-application.png, import-existing-application.png,
out-3.ogv
In the New OpenShift Application wizard, user has two choices 1) use existing app or 2)
create new app.
* If user clicks 'Use my existing OpenShift application', then list of cartridges
should be disabled. I was able to give name of app to import and then select cartridge
which was meaningless as app was imported with original cartridge (as expected) and not
the new one I had selected.
* If user clicks 'Create a new OpenShift application', the field for app name
and browse button should be disabled.
But this also raises the question for me as to why these two choices are shared on the
same wizard page. I wonder if it would be cleaner to separate them.
* So when in OpenShift Explorer view a user right-clicks an application and clicks
'Import Application' they would just see the wizard starting from the page
'Set up project for new OpenShift Application'. They've already decided they
want to import so offering fields about creating a new OpenShift app isn't useful.
* Similarly, when a user selects 'New > Application' then they don't need
to be offered the information about using an existing OpenShift application. To me as a
user, the action 'New > Application' makes me thing that I am creating a new
OpenShift Application so having fields about using an existing OpenShift app is confusing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira