[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22079:
----------------------------------------
Assignee: (was: Andre Dietisheim)
> Error when import a project already existing in workspace
> ---------------------------------------------------------
>
> Key: JBIDE-22079
> URL: https://issues.jboss.org/browse/JBIDE-22079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: import-error.png
>
>
> When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear).
> Error:
> {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts.
> One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again.
> An exception stack trace is not available.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21818) Too large margins in wizards
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21818:
-------------------------------------
Priority: Minor (was: Major)
> Too large margins in wizards
> ----------------------------
>
> Key: JBIDE-21818
> URL: https://issues.jboss.org/browse/JBIDE-21818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2016-03-04 11.19.59.png
>
>
> Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general.
> See attached screenshot as an example
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22186) Connection (wizard): OpenShift asks for a password when CDK is restarted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22186?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22186:
-------------------------------------
Summary: Connection (wizard): OpenShift asks for a password when CDK is restarted (was: OpenShift asks for a password when CDK is restarted)
> Connection (wizard): OpenShift asks for a password when CDK is restarted
> ------------------------------------------------------------------------
>
> Key: JBIDE-22186
> URL: https://issues.jboss.org/browse/JBIDE-22186
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> 1. Install JBDS 9.1 using our windows installer
> 2. Start CDK. Enter your red hat accaunt/password and check "save password"
> 3. CDK is started. OS connection is available. I can open it and work with it.
> 4. Stop CDK. Re-start JBDS/Eclipse.
> 5. Start CDK again.
> 6. Go to OS explorer is try to unfold the connection.
> 7. I'm being asked for the OS password for the "openshift-dev" user. I see that "save password" is not checked.
> It's very confusing because if I'm not familiar with OS I have no idea what password I'm supposed to use. And this connection worked fine before I restarted Eclipse/CDK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22186) Connection (wizard): OpenShift asks for a password when CDK is restarted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22186?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22186:
-------------------------------------
Labels: connection_wizard openshift_v3 (was: )
> Connection (wizard): OpenShift asks for a password when CDK is restarted
> ------------------------------------------------------------------------
>
> Key: JBIDE-22186
> URL: https://issues.jboss.org/browse/JBIDE-22186
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> 1. Install JBDS 9.1 using our windows installer
> 2. Start CDK. Enter your red hat accaunt/password and check "save password"
> 3. CDK is started. OS connection is available. I can open it and work with it.
> 4. Stop CDK. Re-start JBDS/Eclipse.
> 5. Start CDK again.
> 6. Go to OS explorer is try to unfold the connection.
> 7. I'm being asked for the OS password for the "openshift-dev" user. I see that "save password" is not checked.
> It's very confusing because if I'm not familiar with OS I have no idea what password I'm supposed to use. And this connection worked fine before I restarted Eclipse/CDK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21068) Project wizard: Set maximum length for display name
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21068?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21068:
-------------------------------------
Labels: openshift_v3 project_wizard (was: openshift_v3)
> Project wizard: Set maximum length for display name
> ---------------------------------------------------
>
> Key: JBIDE-21068
> URL: https://issues.jboss.org/browse/JBIDE-21068
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jan Richter
> Priority: Minor
> Labels: openshift_v3, project_wizard
> Fix For: 4.4.0.Alpha1
>
>
> Currently the 'Display Name' text field has no length limit. OpenShift on the other hand will only allow fields of length up to 65536 characters. Would be nice to let the user only input a valid length string.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months