[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-21302:
-------------------------------
Component/s: common/jst/core
(was: server)
> Removing user from credentials framework while not authenticated to secure storage should not work
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21302
> URL: https://issues.jboss.org/browse/JBIDE-21302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
> Reporter: Radim Hopp
> Assignee: Rob Stryker
>
> Removing credentials (which are stored in secure storage) using
> CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-21302:
----------------------------------
Summary: Removing user from credentials framework while not authenticated to secure storage should not work
Key: JBIDE-21302
URL: https://issues.jboss.org/browse/JBIDE-21302
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.1.Beta1
Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
Reporter: Radim Hopp
Removing credentials (which are stored in secure storage) using
CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ]
Radim Hopp reassigned JBIDE-21302:
----------------------------------
Assignee: Rob Stryker
> Removing user from credentials framework while not authenticated to secure storage should not work
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21302
> URL: https://issues.jboss.org/browse/JBIDE-21302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
> Reporter: Radim Hopp
> Assignee: Rob Stryker
>
> Removing credentials (which are stored in secure storage) using
> CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21050) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21050?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-21050:
----------------------------------
Fix Version/s: 4.3.1.Beta2
> webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21050
> URL: https://issues.jboss.org/browse/JBIDE-21050
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Rob Stryker
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.3.1.Beta2
>
>
> WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules.
> The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later.
> The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb.
> See also: https://issues.jboss.org/browse/JBIDE-20802
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21133) Improve the 'Deploy Docker Image to Openshift' experience
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21133?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21133.
---------------------------------
Verified on nightly build having OpenShift tooling of version v20151211-0336-B118. Search button next to image text widget covers user experience pretty nice.
> Improve the 'Deploy Docker Image to Openshift' experience
> ---------------------------------------------------------
>
> Key: JBIDE-21133
> URL: https://issues.jboss.org/browse/JBIDE-21133
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: docker, openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Labels: openshift_v3
> Fix For: 4.3.1.Beta1
>
> Attachments: 00000568.png, Screenshot 2015-11-24 09.46.08.png
>
>
> Deploy to Openshift from Docker Explorer (see screenshot below)
> The resulting dialog (attached)
> - promotes me for my Openshift - since I only have one connection - it should default to the one and only one connection
> - Image: wants "repo", "name" and "tag" - well, with the PDK, this image is already "IN" OpenShift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21072) Application wizard: Server templates tree is not rendered
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21072?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21072.
---------------------------------
Verified on nightly build having OpenShift tooling of version v20151211-0336-B118.
> Application wizard: Server templates tree is not rendered
> ---------------------------------------------------------
>
> Key: JBIDE-21072
> URL: https://issues.jboss.org/browse/JBIDE-21072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Labels: application_wizard, openshift_v3, upstream
> Fix For: 4.3.1.Beta1
>
> Attachments: wizard.png
>
>
> When I select at first a local template then proceed to next wizard page in a New OpenShift Application wizard and hit back button then tree containing server templates is not rendered correctly. Only search text field is shown but the tree with templates is missing there.
> !wizard.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20531.
---------------------------------
Verified on nightly build having OpenShift tooling of version v20151211-0336-B118.
> Expose additional service ports from deploy docker image wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-20531
> URL: https://issues.jboss.org/browse/JBIDE-20531
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: docker
> Fix For: 4.3.1.Beta1
>
> Attachments: PortWindow.png, Service and routing page.png, service port edit dialog.png
>
>
> Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image
> * Also only remove those which were added
> * Only reset those which are defaults
> * Edit via double click
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21301) Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21301:
-------------------------------------
Summary: Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH
Key: JBIDE-21301
URL: https://issues.jboss.org/browse/JBIDE-21301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Marián Labuda
In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months