March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3243) as a JavaEE developer I would like to be able to use newest features of the JavaEE platform so I can be more effective

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3243?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3243: ----------------------------- CDW release: + (was: ?) > as a JavaEE developer I would like to be able to use newest features of the JavaEE platform so I can be more effective > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3243 > URL: https://issues.jboss.org/browse/JBDS-3243 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: cdi, hibernate, jsp/jsf/xml/html source editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 9.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3244: -------------------------------------- CDW devel_ack: + (was: ?) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html source editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3244: ----------------------------- CDW release: + (was: ?) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html source editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3244: -------------------------------- > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html source editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3245) Improve Eclipse Platform

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3245: -------------------------------------- CDW devel_ack: + (was: ?) > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3245) Improve Eclipse Platform

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3245: -------------------------------- > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3245) Improve Eclipse Platform

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3245?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3245: ----------------------------- CDW release: + (was: ?) > Improve Eclipse Platform > ------------------------ > > Key: JBDS-3245 > URL: https://issues.jboss.org/browse/JBDS-3245 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 9.0.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- 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 CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3250: -------------------------------- > 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, requirements > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 9.0.0.GA > > > 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) (JBDS-3306) > {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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3250: -------------------------------------- CDW devel_ack: + (was: ?) > 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, requirements > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 9.0.0.GA > > > 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) (JBDS-3306) > {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 CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3250: ----------------------------- CDW release: + (was: ?) > 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, requirements > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 9.0.0.GA > > > 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) (JBDS-3306) > {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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2015