June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22593: -------------------------------- Story Points: 9 > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22593: -------------------------------- Sprint: devex #116 June 2016 > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22362: -------------------------------- Sprint: devex #116 June 2016 > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Alpha1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22362: -------------------------------- Story Points: 4 > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Alpha1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22362: ----------------------------------- Assignee: Marián Labuda (was: Ilya Buziuk) > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Alpha1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20002) Explorer: Delete multiple OpenShift resources at once

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20002?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20002: ------------------------------------------ [~jeffmaury] isnt JBIDE-22241 that you're working on including this? > Explorer: Delete multiple OpenShift resources at once > ----------------------------------------------------- > > Key: JBIDE-20002 > URL: https://issues.jboss.org/browse/JBIDE-20002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > > It would be nice to have a feature allowing removing more resources at once: > 1) Multiselect on some specific type of resource (e.g. pods) and deleting them via context menu "Delete resources..." which pop up dialog "Do you really want to delete selected resources?" with Yes, No, Cancel. > 2) Deleting specific resources - from context menu on Pods / Builds etc. I would like to choose "Delete resources..." to remove all underlying resources. > 3) Delete all resources. Should be accessible from context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ] Xavier Coulon updated JBDS-3551: -------------------------------- Fix Version/s: (was: 9.x) > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 10.x > > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9442) Investigate possibility for remote debug launch of app servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9442?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-9442: ------------------------------- Story Points: 3 > Investigate possibility for remote debug launch of app servers > -------------------------------------------------------------- > > Key: JBIDE-9442 > URL: https://issues.jboss.org/browse/JBIDE-9442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.1.Alpha1 > > > When launching a remote server on a remote host, we do not currently connect a remote debugger. It'd be nice if we also connected a remote debugger if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-743) Guvnor is still available on the update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-743?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-743. ----------------------------------- Verified > Guvnor is still available on the update site > -------------------------------------------- > > Key: JBTIS-743 > URL: https://issues.jboss.org/browse/JBTIS-743 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.0.0.Alpha1 > > > The following update site > http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > contains Guvnor feature which should be removed in Neon release (like ESB and jBPM3). > Note that the feature is not included in any category but it is available if you uncheck 'Group items by category'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-742) Update Teiid Designer in Devstudio IS 10.0.0.Alpha1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-742?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-742. ----------------------------------- Verified, now it contains Teiid Designer 10.0.1.Beta1-v20160524-2113-B1 > Update Teiid Designer in Devstudio IS 10.0.0.Alpha1 > --------------------------------------------------- > > Key: JBTIS-742 > URL: https://issues.jboss.org/browse/JBTIS-742 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: build, teiid > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.0.0.Alpha1 > > > Please update the version of Teiid Designer to 10.0.1.Beta1 in Devstudio IS 10.0.0.Alpha1-SNAPSHOT. My point is not to have older version of TD in Neon (TD 10.0.0.Beta3) than in Mars (TD 10.0.1.Beta1). > Moreover, this will help QE to use the same tests for both Mars and Neon at the moment. Currently, this is not possible since there is a different 'New Project' wizard in TD 10.0.1.Beta1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 June 2016