[JBoss JIRA] (JBIDE-21331) Connection wizard: it looks as if the wizard is creating new connection instances several times
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21331:
----------------------------------------
Summary: Connection wizard: it looks as if the wizard is creating new connection instances several times
Key: JBIDE-21331
URL: https://issues.jboss.org/browse/JBIDE-21331
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Andre Dietisheim
Priority: Minor
The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification)
{code:title:ConnctionWizardPageModel}
private void initEditConnection(IConnection connection) {
this.selectedConnection = connection;
this.connection = connection.clone();
...
{code}
{code:title:ConnctionWizardPageModel}
public IStatus connect() {
...
try {
this.connection = createConnection();
...
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21331) Connection wizard: it looks as if the wizard is creating new connection instances several times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21331?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21331:
-------------------------------------
Description:
The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification)
{code:title=ConnctionWizardPageModel}
private void initEditConnection(IConnection connection) {
this.selectedConnection = connection;
this.connection = connection.clone();
...
{code}
{code:title=ConnctionWizardPageModel}
public IStatus connect() {
...
try {
this.connection = createConnection();
...
{code}
was:
The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification)
{code:title:ConnctionWizardPageModel}
private void initEditConnection(IConnection connection) {
this.selectedConnection = connection;
this.connection = connection.clone();
...
{code}
{code:title:ConnctionWizardPageModel}
public IStatus connect() {
...
try {
this.connection = createConnection();
...
{code}
> Connection wizard: it looks as if the wizard is creating new connection instances several times
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-21331
> URL: https://issues.jboss.org/browse/JBIDE-21331
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Priority: Minor
>
> The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification)
> {code:title=ConnctionWizardPageModel}
> private void initEditConnection(IConnection connection) {
> this.selectedConnection = connection;
> this.connection = connection.clone();
> ...
> {code}
> {code:title=ConnctionWizardPageModel}
> public IStatus connect() {
> ...
> try {
> this.connection = createConnection();
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21325) Connection wizard: trying to login with expired token causes 2nd, nested connection dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21325?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21325:
------------------------------------------
This changed with JBIDE-21153. Before this the prompting didnt happen because there was no prompter available. Since JBIDE-21153 where we use extension points there's always a credentials-prompt available which caused this issue.
To fix it I now introduced a flag which allows us to turn prompting off when we're in the credentials dialog
[~fbricon] plz review
> Connection wizard: trying to login with expired token causes 2nd, nested connection dialog
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21325
> URL: https://issues.jboss.org/browse/JBIDE-21325
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: connection_wizard, openshift_v3, respin-a
> Fix For: 4.3.1.Beta1, 4.3.1.Beta2
>
> Attachments: nested-2nd-conncetion-dialog.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21244) OpenShift New and Noteworthy for 4.3.1.Beta1
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21244?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21244:
-------------------------------------
== CDK Server Adapter
A new server adapter has been added to help start and stop the Red Hat Container Development Kit, a set of tools meant to quickly set up an Openshift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, docker and Openshift connections should appear in their respective views, allowing the user to quickly create a new Openshift application and begin developing their AwesomeApp in a highly-replicatable environment.
This plugin is still very experimental, mainly due to the rapidly changing fast-paced development going on in the underlying CDK. For Windows users, at least, an installer will be available to help set up the environment and install all pre-requisites for the CDK. Once installed, simply running the bundled JBDS should automatically create the CDK server adapter in your workspace, and allow you to get started right away by simply starting the CDK server as you would any other server adapter inside JBoss Tools.
> OpenShift New and Noteworthy for 4.3.1.Beta1
> --------------------------------------------
>
> Key: JBIDE-21244
> URL: https://issues.jboss.org/browse/JBIDE-21244
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.3.1.Beta1
>
>
> This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...].
> If OpenShift is not listed here check if there are issues that should be added and add them.
> Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request.
> If no news for this component please reject and close this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months