March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3711) JBDS setup is called after installation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3711?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3711: ------------------------------ Description: What the setup does is it replaces the -vm path to the new installation in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation. (was: What the setup does is it checks if the user selected to install JDK and if so it replaces the -vm path to the new installation in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation.) > JBDS setup is called after installation > --------------------------------------- > > Key: JBDS-3711 > URL: https://issues.jboss.org/browse/JBDS-3711 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > > What the setup does is it replaces the -vm path to the new installation in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3711) JBDS setup is called after installation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3711?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3711: ------------------------------ Description: What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation. (was: What the setup does is it replaces the -vm path to the new installation in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation.) > JBDS setup is called after installation > --------------------------------------- > > Key: JBDS-3711 > URL: https://issues.jboss.org/browse/JBDS-3711 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > > What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3711) JBDS setup is called after installation

by Jan Richter (JIRA)

Jan Richter created JBDS-3711: --------------------------------- Summary: JBDS setup is called after installation Key: JBDS-3711 URL: https://issues.jboss.org/browse/JBDS-3711 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Reporter: Jan Richter Assignee: Denis Golovin What the setup does is it checks if the user selected to install JDK and if so it replaces the -vm path to the new installation in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21949?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21949: ---------------------------------- Sprint: devex #4 March 2016 > Allow user to turn on/off showing console when output changes > ------------------------------------------------------------- > > Key: JBIDE-21949 > URL: https://issues.jboss.org/browse/JBIDE-21949 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21949?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21949: ---------------------------------- Component/s: server > Allow user to turn on/off showing console when output changes > ------------------------------------------------------------- > > Key: JBIDE-21949 > URL: https://issues.jboss.org/browse/JBIDE-21949 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21864) Server Adapter: publishing is slow compared to "oc rsync" on the cmd line

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21864?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21864: --------------------------------------- coud this be improved with JBIDE-21453 being resolved ? > Server Adapter: publishing is slow compared to "oc rsync" on the cmd line > ------------------------------------------------------------------------- > > Key: JBIDE-21864 > URL: https://issues.jboss.org/browse/JBIDE-21864 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Compared with "oc rsync" on the cmd line publishing in the server adapter (which does "oc rsync" behind the scenes) is very slow -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21864) Server Adapter: publishing is slow compared to "oc rsync" on the cmd line

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21864?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-21864 at 3/24/16 5:39 AM: ---------------------------------------------------------------- Now that JBIDE-21453 has been resolved, can you see some performance improvements ? was (Author: xcoulon): coud this be improved with JBIDE-21453 being resolved ? > Server Adapter: publishing is slow compared to "oc rsync" on the cmd line > ------------------------------------------------------------------------- > > Key: JBIDE-21864 > URL: https://issues.jboss.org/browse/JBIDE-21864 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Compared with "oc rsync" on the cmd line publishing in the server adapter (which does "oc rsync" behind the scenes) is very slow -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21965) oc rsync triggered when adding/removing breakpoints

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21965?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21965: ---------------------------------- Sprint: devex #4 March 2016 > oc rsync triggered when adding/removing breakpoints > --------------------------------------------------- > > Key: JBIDE-21965 > URL: https://issues.jboss.org/browse/JBIDE-21965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Fix For: 4.3.1.CR1 > > > With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered. > in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs. > AFTER | BEFORE > !http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-609) Create tests for project deletion

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-609?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík resolved JBTIS-609. -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Final) Resolution: Done > Create tests for project deletion > --------------------------------- > > Key: JBTIS-609 > URL: https://issues.jboss.org/browse/JBTIS-609 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.CR1 > > Time Spent: 1 hour > Remaining Estimate: 0 minutes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21453) Server Adapter: use rsync flag instead of local filtered-copy

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21453?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21453: --------------------------------------- Steps to verify: during the rsync operation (now displayed in a console), there should be not reference to the content of the {{.git}} directory copied from the pod to the local deployment directory (some directory in the workspace metadata, eg: {{.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@nodejs-example/deploy}} > Server Adapter: use rsync flag instead of local filtered-copy > ------------------------------------------------------------- > > Key: JBIDE-21453 > URL: https://issues.jboss.org/browse/JBIDE-21453 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > With https://github.com/openshift/origin/issues/6143 *oc rsync* now allows specific white-listed flag to be used. > Our current implementation works around this by doing a local copy where excluded bits are filtered (not copied). We need to use exclusion flags if available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2016