July 2015 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------------- JBDS-3489 covers the new app usecases. > 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, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > 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.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20325) WildFly server has wrong case in server name

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20325?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20325: -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > WildFly server has wrong case in server name > -------------------------------------------- > > Key: JBIDE-20325 > URL: https://issues.jboss.org/browse/JBIDE-20325 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.0.CR1 > > > When you add a WildFly server using runtime detection, the runtime will be called Wildfly (notice the lower case "f") and same is true for the server name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3484) Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3484?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3484. ---------------------------------- Fix Version/s: 9.0.0.Beta2 Resolution: Done This issue was fixed for Beta2 respin-a. We don't have the respin-a available yet. Resolving the issue. Please verify it in respin-a. > Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3484 > URL: https://issues.jboss.org/browse/JBDS-3484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: javascript > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.Beta2 > > > Currently org.jboss.tools.jst.js.feature with bower integration available only from jbosstools aggregated p2 repository. > This is very desired feature for javascript development and should be included into into JBDS installer, BYOE feature and JBDS p2 repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20370) When an Openshift project is created, make sure the Openshift Explorer is displayed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20370?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20370: -------------------------------- Fix Version/s: 4.3.0.CR1 > When an Openshift project is created, make sure the Openshift Explorer is displayed > ------------------------------------------------------------------------------------ > > Key: JBIDE-20370 > URL: https://issues.jboss.org/browse/JBIDE-20370 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Fix For: 4.3.0.CR1 > > > If I try to create a new Application on OpenShift v3, it'll create a Project first, then an application from a template on that project. Nothing shows up in Eclipse once I'm done, this is utterly confusing. At the very least, at the end, the OpenShift Explorer should be displayed, to let me know *something* happened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20370) When an Openshift project is created, make sure the Openshift Explorer is displayed

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-20370: ----------------------------------- Summary: When an Openshift project is created, make sure the Openshift Explorer is displayed Key: JBIDE-20370 URL: https://issues.jboss.org/browse/JBIDE-20370 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Fred Bricon If I try to create a new Application on OpenShift v3, it'll create a Project first, then an application from a template on that project. Nothing shows up in Eclipse once I'm done, this is utterly confusing. At the very least, at the end, the OpenShift Explorer should be displayed, to let me know *something* happened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] Jeff Cantrill updated JBDS-3489: -------------------------------- Description: As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. * This is equivalent to 'oc new-app' was: As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 9.0.0.CR1 > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20173) Clean up UI errors in case RSE is not installed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20173?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20173: ------------------------------------- It shouldn't really happen anymore, but, theoretically, someone could be using our stuff without the rse integration ;) Um... you could check out our source code... and then... comment out: {code} <includes id="org.jboss.ide.eclipse.as.server.rse.integration.feature" version="0.0.0"/> {code} In jbosstools-server/as/features/org.jboss.ide.eclipse.as.feature/feature.xml And then build it, and then install from the local site? I think that should do it. > Clean up UI errors in case RSE is not installed > ----------------------------------------------- > > Key: JBIDE-20173 > URL: https://issues.jboss.org/browse/JBIDE-20173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > In an environment where RSE is not available, the UI fails in multiple fashions. It allows you to create RSE servers, even though it shouldn't. If there's a previously-existing RSE server, the server editor will fail to load with NPE. There is also no warning in the editor anywhere indicating that the server is incompatible with current profile. > Also, start / debug / etc should fail indicating profile is unavailable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19850: ------------------------------------------ It very much looks like there's a problem in the server or "oc" binary that we cant fix for now. We're releasing 4.3.0.Beta2 with this broken unfortunately. Postponing to 4.3.0.CR1 > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: hello_world_template.json > > > As a user I want to be able to easily set up port forwarding to my application > Test by: > # Start OpenShift > # Create app from attached template > # Right Click on "Hello-world Pod" > Forward Ports > # Check find open ports > # Start Port forwarding > # In a terminal "curl localhost:<assigned local port>" > # Expect "Hello OpenShift" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19850: ------------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: hello_world_template.json > > > As a user I want to be able to easily set up port forwarding to my application > Test by: > # Start OpenShift > # Create app from attached template > # Right Click on "Hello-world Pod" > Forward Ports > # Check find open ports > # Start Port forwarding > # In a terminal "curl localhost:<assigned local port>" > # Expect "Hello OpenShift" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19850: ------------------------------------- Labels: openshift_v3 port_forwarding_wizard (was: openshift_v3 port_forwarding_wizard respin-a) > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: hello_world_template.json > > > As a user I want to be able to easily set up port forwarding to my application > Test by: > # Start OpenShift > # Create app from attached template > # Right Click on "Hello-world Pod" > Forward Ports > # Check find open ports > # Start Port forwarding > # In a terminal "curl localhost:<assigned local port>" > # Expect "Hello OpenShift" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 July 2015