[JBoss JIRA] (JBIDE-17903) Explorer, Server Adapter: add show in > project explorer for openshift apps
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17903:
-------------------------------------
Fix Version/s: (was: LATER)
> Explorer, Server Adapter: add show in > project explorer for openshift apps
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17903
> URL: https://issues.jboss.org/browse/JBIDE-17903
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: explorer, openshift_v2, server_adapter
> Fix For: 4.5.3.Final
>
>
> couldn't we have "show in" project explorer enabled for openshift applications ?
> If 0 found -> open dialog "Application 'xyz' not found in workspace. Do you want to import it ?"
> if 1 found -> have it selected in project explorer
> if >1 found -> open dialog "Multiple projects found mapped to application 'xyz' which one do you want ?" (is this even technically possible since the project names would be the same...? - I guess if they are on different branches with different .project names then yes)
> maybe just pick the first found in the >1 found case to keep it simple?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-20126) v2 Import-, application wizard: use easy import, not our custom facility
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20126?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20126:
-------------------------------------
Fix Version/s: (was: LATER)
> v2 Import-, application wizard: use easy import, not our custom facility
> ------------------------------------------------------------------------
>
> Key: JBIDE-20126
> URL: https://issues.jboss.org/browse/JBIDE-20126
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.5.3.Final
>
>
> The current impl of the import wizard in v2 and v3 is using a custom import logic where it launches m2e for repositories that have a pom.xml and "General project" for all the others. In JBDS-3285 [~mickael_istria] contributed a new Easy import facility for Eclipse that we should use instead of our own minimalistic, custom made approach
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22743) SSH keys are not fetched by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22743?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22743:
-------------------------------------
Fix Version/s: (was: LATER)
> SSH keys are not fetched by default
> -----------------------------------
>
> Key: JBIDE-22743
> URL: https://issues.jboss.org/browse/JBIDE-22743
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v2, sshkeys_wizard
> Fix For: 4.5.3.Final
>
>
> In Manage SSH Keys wizard for OpenShift 2 plugin there is a table containing SSH keys uploaded for an OpenShift 2 account. Earlier, if I had uploaded SSH keys elsewhere and then opened Manage SSH Keys shell, those uploaded SSH keys were there by default. Now I have to push Refresh button to get SSH keys.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-12144) EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12144?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12144:
-------------------------------------
Fix Version/s: (was: LATER)
> EGitUtils#push is throwing an exception if push fails. It should use the same semantics as EGit
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-12144
> URL: https://issues.jboss.org/browse/JBIDE-12144
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: cleanup, openshift_v2
> Fix For: 4.5.3.Final
>
>
> EgitUtils#push throws an exception if the push failed because of ex. "non fastforward push".
> {code}
> private static PushOperationResult push(Repository repository, RemoteConfig remoteConfig, boolean force, IProgressMonitor monitor) throws CoreException {
> ...
> PushOperationResult pushResult = op.getOperationResult();
> if (hasFailedEntries(pushResult)) {
> throw new CoreException(
> EGitCoreActivator.createErrorStatus(
> NLS.bind("Could not push repository {0}: {1}",
> repository.toString(), getErrors(pushResult))
> , null));
> }
> return pushResult;
> {code}
> EGit is not throwing an exception in this case. You simply get the failure in the PushResult object you'll have to look at.
> EGitUtils#push is thus changing the API semantics of EGit and it shouldn't.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19654:
-------------------------------------
Fix Version/s: (was: LATER)
> Application wizard: Opening the wizard on an account without SSH key opens broken wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19654
> URL: https://issues.jboss.org/browse/JBIDE-19654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v2
> Fix For: 4.5.3.Final
>
> Attachments: new_app_wizard.png, prompt-to-upload-keys.png
>
>
> If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty
> !new_app_wizard.png!
> There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-12571) Connection wizard: Eclipse preferences: allow users to define a default server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12571?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-12571:
----------------------------------------
Fix Version/s: 4.5.3.Final
Assignee: Andre Dietisheim
> Connection wizard: Eclipse preferences: allow users to define a default server
> ------------------------------------------------------------------------------
>
> Key: JBIDE-12571
> URL: https://issues.jboss.org/browse/JBIDE-12571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: connection_wizard, new_and_noteworthy, openshift_v2
> Fix For: 4.5.3.Final, LATER
>
> Attachments: 2012-09-10 13.10.bmml, 2012-09-10 13.10.bmml, 2012-09-10 13.10.png
>
>
> Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled, prefilled with the server that is present in the (rhc cli-tooling) openshift configuration. Once unchecked the user can enter a default server and override the openshift server that is configured in the configuration.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22743) SSH keys are not fetched by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22743?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22743:
----------------------------------------
Fix Version/s: 4.5.3.Final
Assignee: Andre Dietisheim
> SSH keys are not fetched by default
> -----------------------------------
>
> Key: JBIDE-22743
> URL: https://issues.jboss.org/browse/JBIDE-22743
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v2, sshkeys_wizard
> Fix For: 4.5.3.Final, LATER
>
>
> In Manage SSH Keys wizard for OpenShift 2 plugin there is a table containing SSH keys uploaded for an OpenShift 2 account. Earlier, if I had uploaded SSH keys elsewhere and then opened Manage SSH Keys shell, those uploaded SSH keys were there by default. Now I have to push Refresh button to get SSH keys.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months