January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3298: ----------------------------------- [~maxandersen] I would say that is the oversimplified way to look at it. git push is step h, there are also things like i and j to consider. Not to mention a through g which are required before "git push" would work. > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3298: ------------------------------------------- is this anything but just doing git push on the openshift project ? > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18827?page=com.atlassian.jira.plugi... ] Marián Labuda reassigned JBIDE-18827: ------------------------------------- Assignee: Andre Dietisheim (was: Marián Labuda) > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-18827 > URL: https://issues.jboss.org/browse/JBIDE-18827 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Eclipse plugin > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18827?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18827: ------------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-openshift/pull/510) > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-18827 > URL: https://issues.jboss.org/browse/JBIDE-18827 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Eclipse plugin > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18827?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18827: ------------------------------------- Estimated Difficulty: Low (was: High) > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-18827 > URL: https://issues.jboss.org/browse/JBIDE-18827 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Eclipse plugin > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18827?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18827: ------------------------------------- Affects Version/s: 4.2.0.Final > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-18827 > URL: https://issues.jboss.org/browse/JBIDE-18827 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Eclipse plugin > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18827?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18827: ------------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.3.x) > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-18827 > URL: https://issues.jboss.org/browse/JBIDE-18827 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Eclipse plugin > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3275: ---------------------------------------- WFLY-4171 is being blocked by WFLY-4190 . Do you have any idea who could provide those Wildfly banners for us ? Thanks > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBDS-3275 > URL: https://issues.jboss.org/browse/JBDS-3275 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central. > This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3235) Missing properties view for servers elements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3235?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-3235: --------------------------------------- Sprint: Sprint 20141113 > Missing properties view for servers elements > -------------------------------------------- > > Key: JBIDE-3235 > URL: https://issues.jboss.org/browse/JBIDE-3235 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 3.3.x > > > Before I could directly edit properties for ports in properties view. > Now I need to right click and choose Change Value and get a non-standard edit in the tree. > This I could probably live with if I could just double click the value and edit it like in properties view. > Properties view was though also nice to give other details than just access to edit. > i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16720) Server Adapter: Allow easier access to openshift operations from jboss servers

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16720: ---------------------------------------- Sprint: Sprint 20141113 > Server Adapter: Allow easier access to openshift operations from jboss servers > ------------------------------------------------------------------------------ > > Key: JBIDE-16720 > URL: https://issues.jboss.org/browse/JBIDE-16720 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.1.1.Final > Reporter: Mark Drilling > Assignee: Andre Dietisheim > Labels: server_adapter > Fix For: 4.3.x > > > We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case. > Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push. > Currently, we connect to an OpenShift DV instance like this: > 1) Deploy DV cartridge via OpenShift web console. > 2) Port forward from command line using rhc port-forward > 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective > The issues we observed: > 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo. > 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list. > Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015