January 2015 - jbosstools-issues - Jboss List Archives

[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 edited comment on JBIDE-19000 at 1/6/15 4:14 PM: ------------------------------------------------------------------ 1st prototype, explorer showing "simplified" items for v3 and have 2nd "advanced" view (~raw object dump) (copied from JBDS-3278) was (Author: adietish): 1st prototype, explorer showing "simplified" items for v3 and have 2nd "advanced" view (~raw object dump) (copied from JBDS-2378) > 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 > Attachments: 2015-01-06 22.13.bmml, 2015-01-06 22.13.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[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: ------------------------------------------ 1st prototype, explorer showing "simplified" items for v3 and have 2nd "advanced" view (~raw object dump) > 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 > Attachments: 2015-01-06 22.13.bmml, 2015-01-06 22.13.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[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 edited comment on JBIDE-19000 at 1/6/15 4:14 PM: ------------------------------------------------------------------ 1st prototype, explorer showing "simplified" items for v3 and have 2nd "advanced" view (~raw object dump) (copied from JBDS-2378) was (Author: adietish): 1st prototype, explorer showing "simplified" items for v3 and have 2nd "advanced" view (~raw object dump) > 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 > Attachments: 2015-01-06 22.13.bmml, 2015-01-06 22.13.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18999) As a user I want to connect to a v3 OpenShift instance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18999?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18999: ------------------------------------- Comment: was deleted (was: 1st prototype, explorer showing "simplified" items for v3 and have 2nd "advanced" view (~raw object dump)) > As a user I want to connect to a v3 OpenShift instance > ------------------------------------------------------ > > Key: JBIDE-18999 > URL: https://issues.jboss.org/browse/JBIDE-18999 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Labels: openshift-v3 > Attachments: 2015-01-06 22.09.bmml > > > * Ignore auth for now > * The connection should be usable to retrieve Kubernetes resources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18999) As a user I want to connect to a v3 OpenShift instance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18999?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18999: ------------------------------------- Attachment: (was: 2015-01-06 22.09.png) > As a user I want to connect to a v3 OpenShift instance > ------------------------------------------------------ > > Key: JBIDE-18999 > URL: https://issues.jboss.org/browse/JBIDE-18999 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Labels: openshift-v3 > Attachments: 2015-01-06 22.09.bmml > > > * Ignore auth for now > * The connection should be usable to retrieve Kubernetes resources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18999) As a user I want to connect to a v3 OpenShift instance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18999?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18999: ------------------------------------------ 1st prototype, explorer showing "simplified" items for v3 and have 2nd "advanced" view (~raw object dump) > As a user I want to connect to a v3 OpenShift instance > ------------------------------------------------------ > > Key: JBIDE-18999 > URL: https://issues.jboss.org/browse/JBIDE-18999 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Labels: openshift-v3 > Attachments: 2015-01-06 22.09.bmml, 2015-01-06 22.09.png > > > * Ignore auth for now > * The connection should be usable to retrieve Kubernetes resources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3250) Support for OpenShift 3 with Docker and Kubernetes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3250: ----------------------------------- Description: Copied from JBDS-3278 As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API. The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture. For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"): {quote} It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo…. Our Eclipse end-user needs to be able to “browse” for it and select it git clone it make changes git push it back {quote} This gives us 3 main use cases (as in mail and chats): # Import existing OpenShift project (JBDS-3297) # Push Changes to Existing OpenShift project (JBDS-3298) # New Project from Template (template should have a default buildconfig, deployconfig and docker image) {quote} Use Case #1 assumes a TON about what has happened before me. - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL - Assumes end-user is already logged in (there is no auth method at this time) - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc. {quote} We have a more extensive document that outlines the usecases: https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_... {quote} These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling: 1) Create SSH Keys 2) Upload SSH Keys 3) Create Domain 4) Add a database, message broker, cache (embeddable cartridge) 5) Show In Web Browser 6) Review Env Vars 7) Edit Env Vars 8) Review Logs 9) Log Streaming 10) SSH in 11) Delete/Destroy 12) Remote Debugging (though that might "just work") 13) Snapshot creation 14) Snapshot restore 15) Port Forwarding 16) Marker Files 17) Node.js 18) PHP 19) Python 20) C++ 21) Perl {quote} was: Copied from JBDS-3278 As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API. The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture. For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"): {quote} It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo…. Our Eclipse end-user needs to be able to “browse” for it and select it git clone it make changes git push it back {quote} This gives us 3 main use cases (as in mail and chats): # Import existing OpenShift project (JBDS-3297) # Push Changes to Existing OpenShift project (JBDS-3298) # New Project from Template (template should have a default buildconfig, deployconfig and docker image) {quote} Use Case #1 assumes a TON about what has happened before me. - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL - Assumes end-user is already logged in (there is no auth method at this time) - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc. {quote} We have a more extensive document that outlines the usecases: https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_... {quote} These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling: 1) Create SSH Keys 2) Upload SSH Keys 3) Create Domain 4) Add a database, message broker, cache (embeddable cartridge) 5) Show In Web Browser 6) Review Env Vars 7) Edit Env Vars 8) Review Logs 9) Log Streaming 10) SSH in 11) Delete/Destroy 12) Remote Debugging (though that might "just work") 13) Snapshot creation 14) Snapshot restore 15) Port Forwarding 16) Marker Files 17) Node.js 18) PHP 19) Python 20) C++ 21) Perl {quote} > Support for OpenShift 3 with Docker and Kubernetes > -------------------------------------------------- > > Key: JBDS-3250 > URL: https://issues.jboss.org/browse/JBDS-3250 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > Copied from JBDS-3278 > As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API. > The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture. > For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"): > {quote} > It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo…. > Our Eclipse end-user needs to be able to “browse” for it and select it > git clone it > make changes > git push it back > {quote} > This gives us 3 main use cases (as in mail and chats): > # Import existing OpenShift project (JBDS-3297) > # Push Changes to Existing OpenShift project (JBDS-3298) > # New Project from Template (template should have a default buildconfig, deployconfig and docker image) > {quote} > Use Case #1 assumes a TON about what has happened before me. > - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL > - Assumes end-user is already logged in (there is no auth method at this time) > - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc. > {quote} > We have a more extensive document that outlines the usecases: > https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_... > {quote} > These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling: > 1) Create SSH Keys > 2) Upload SSH Keys > 3) Create Domain > 4) Add a database, message broker, cache (embeddable cartridge) > 5) Show In Web Browser > 6) Review Env Vars > 7) Edit Env Vars > 8) Review Logs > 9) Log Streaming > 10) SSH in > 11) Delete/Destroy > 12) Remote Debugging (though that might "just work") > 13) Snapshot creation > 14) Snapshot restore > 15) Port Forwarding > 16) Marker Files > 17) Node.js > 18) PHP > 19) Python > 20) C++ > 21) Perl > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3250) Support for OpenShift 3 with Docker and Kubernetes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3250: ----------------------------------- Description: Copied from JBDS-3278 As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API. The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture. For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"): {quote} It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo…. Our Eclipse end-user needs to be able to “browse” for it and select it git clone it make changes git push it back {quote} This gives us 3 main use cases (as in mail and chats): # Import existing OpenShift project (JBDS-3297) # Push Changes to Existing OpenShift project (JBDS-3298) # New Project from Template (template should have a default buildconfig, deployconfig and docker image) {quote} Use Case #1 assumes a TON about what has happened before me. - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL - Assumes end-user is already logged in (there is no auth method at this time) - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc. {quote} We have a more extensive document that outlines the usecases: https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_... {quote} These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling: 1) Create SSH Keys 2) Upload SSH Keys 3) Create Domain 4) Add a database, message broker, cache (embeddable cartridge) 5) Show In Web Browser 6) Review Env Vars 7) Edit Env Vars 8) Review Logs 9) Log Streaming 10) SSH in 11) Delete/Destroy 12) Remote Debugging (though that might "just work") 13) Snapshot creation 14) Snapshot restore 15) Port Forwarding 16) Marker Files 17) Node.js 18) PHP 19) Python 20) C++ 21) Perl {quote} > Support for OpenShift 3 with Docker and Kubernetes > -------------------------------------------------- > > Key: JBDS-3250 > URL: https://issues.jboss.org/browse/JBDS-3250 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > Copied from JBDS-3278 > As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API. > The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture. > For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"): > {quote} > It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo…. > Our Eclipse end-user needs to be able to “browse” for it and select it > git clone it > make changes > git push it back > {quote} > This gives us 3 main use cases (as in mail and chats): > # Import existing OpenShift project (JBDS-3297) > # Push Changes to Existing OpenShift project (JBDS-3298) > # New Project from Template (template should have a default buildconfig, deployconfig and docker image) > {quote} > Use Case #1 assumes a TON about what has happened before me. > - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL > - Assumes end-user is already logged in (there is no auth method at this time) > - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc. > {quote} > We have a more extensive document that outlines the usecases: > https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_... > {quote} > These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling: > 1) Create SSH Keys > 2) Upload SSH Keys > 3) Create Domain > 4) Add a database, message broker, cache (embeddable cartridge) > 5) Show In Web Browser > 6) Review Env Vars > 7) Edit Env Vars > 8) Review Logs > 9) Log Streaming > 10) SSH in > 11) Delete/Destroy > 12) Remote Debugging (though that might "just work") > 13) Snapshot creation > 14) Snapshot restore > 15) Port Forwarding > 16) Marker Files > 17) Node.js > 18) PHP > 19) Python > 20) C++ > 21) Perl > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19002) Update Tern.java (TP) and AngularJS (Central) IDE v.0.8

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19002?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19002: -------------------------------------- Assignee: Denis Golovin > Update Tern.java (TP) and AngularJS (Central) IDE v.0.8 > ------------------------------------------------------- > > Key: JBIDE-19002 > URL: https://issues.jboss.org/browse/JBIDE-19002 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, jsp/jsf/xml/html source editing, target-platform > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > Let's update them in master ASAP and let's see how it goes then do the same in 4.2.x branch -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19002) Update Tern.java (TP) and AngularJS (Central) IDE v.0.8

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19002?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19002: ----------------------------------- Description: Let's update them in master ASAP and let's see how it goes then do the same in 4.2.x branch (was: Let's update ASAP in master and let's see how it goes then do the same in 4.2.x branch) > Update Tern.java (TP) and AngularJS (Central) IDE v.0.8 > ------------------------------------------------------- > > Key: JBIDE-19002 > URL: https://issues.jboss.org/browse/JBIDE-19002 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, jsp/jsf/xml/html source editing, target-platform > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > Let's update them in master ASAP and let's see how it goes then do the same in 4.2.x branch -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015