[JBoss JIRA] (JBIDE-19263) Add sslcertcallback for v2 since its null
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19263?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19263 at 2/16/15 8:14 AM:
-------------------------------------------------------------------
This was initially intended for 4.3.0.Alpha1 but we decided not to release the current state which we considered not good enough. Postponing to 4.3.0.Alpha2
was (Author: adietish):
This was initially intended for 4.3.0.Alpha1 but we decided not to release the current state which we considered not good enough. Postponing to 4.3.0.Beta1
> Add sslcertcallback for v2 since its null
> -----------------------------------------
>
> Key: JBIDE-19263
> URL: https://issues.jboss.org/browse/JBIDE-19263
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19162?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19162 at 2/16/15 8:02 AM:
-------------------------------------------------------------------
This was initially intended for 4.3.0.Alpha1 but we decided not to release the current state which we considered not good enough. Postponing to 4.3.0.Alpha2
was (Author: adietish):
This was initially intended for 4.3.0.Alpha1 but we decided not to release the current state which we considered not good enough. Postponing to 4.3.0.Beta1
> add new plugins to openshift pom and create feature
> ---------------------------------------------------
>
> Key: JBIDE-19162
> URL: https://issues.jboss.org/browse/JBIDE-19162
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19095) OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19095:
-------------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Beta1)
> OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19095
> URL: https://issues.jboss.org/browse/JBIDE-19095
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: environment_variables
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: erroneous-snapshot-restore-title.png
>
>
> While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19096:
-------------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Beta1)
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha2
>
> Attachments: existing-v2-connection.png, fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> the existing UI for v2 OpenShift:
> * new connection:
> !screenshot-openshift-signin.png!
> * existing connection:
> !existing-v2-connection.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19096 at 2/16/15 7:57 AM:
-------------------------------------------------------------------
This was initially intended for 4.3.0.Alpha1 but we decided not to release the current state which we considered not good enough. Postponing to 4.3.0.Alpha2
was (Author: adietish):
This was initially intended for 4.3.0.Alpha1 but we decided not to release the current state which we considered not good enough. Postponing to 4.3.0.Beta1
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha2
>
> Attachments: existing-v2-connection.png, fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> the existing UI for v2 OpenShift:
> * new connection:
> !screenshot-openshift-signin.png!
> * existing connection:
> !existing-v2-connection.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19000) As a user I want to browse the resources for my projects
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19000:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha1)
> As a user I want to browse the resources for my projects
> --------------------------------------------------------
>
> Key: JBIDE-19000
> URL: https://issues.jboss.org/browse/JBIDE-19000
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: 2015-01-06 22.13.bmml, 2015-01-06 22.13.bmml, 2015-01-06 22.13.png, OpenShift console.pdf
>
>
> * Raw view of OpenShift project resources (e.g. services, pods, build configs).
> * Resources will display the relevant labels and selectors to allow a user to infer associations between resources
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19000) As a user I want to browse the resources for my projects
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19000:
------------------------------------------
This was initially intended for 4.3.0.Alpha1 but we decided not to release the current state which we considered not good enough. Postponing to 4.3.0.Beta1
> As a user I want to browse the resources for my projects
> --------------------------------------------------------
>
> Key: JBIDE-19000
> URL: https://issues.jboss.org/browse/JBIDE-19000
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: 2015-01-06 22.13.bmml, 2015-01-06 22.13.bmml, 2015-01-06 22.13.png, OpenShift console.pdf
>
>
> * Raw view of OpenShift project resources (e.g. services, pods, build configs).
> * Resources will display the relevant labels and selectors to allow a user to infer associations between resources
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months