April 2016 - jbosstools-issues - Jboss List Archives

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

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22063: ------------------------------------- Summary: Server Adapter: use rsync flag instead of local filtered-copy Key: JBIDE-22063 URL: https://issues.jboss.org/browse/JBIDE-22063 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

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21453?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21453: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > 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 > > > 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

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22063?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22063: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > Server Adapter: use rsync flag instead of local filtered-copy > ------------------------------------------------------------- > > Key: JBIDE-22063 > URL: https://issues.jboss.org/browse/JBIDE-22063 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 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

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22063?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-22063. ----------------------------------- Resolution: Done > Server Adapter: use rsync flag instead of local filtered-copy > ------------------------------------------------------------- > > Key: JBIDE-22063 > URL: https://issues.jboss.org/browse/JBIDE-22063 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 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

[JBoss JIRA] (JBIDE-22062) OpenShift Explorer : Make Pod/Build distinction more explicit

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22062?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22062: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > OpenShift Explorer : Make Pod/Build distinction more explicit > ------------------------------------------------------------- > > Key: JBIDE-22062 > URL: https://issues.jboss.org/browse/JBIDE-22062 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: ux > Fix For: 4.4.0.Alpha1 > > > After witnessing a new user struggling with pods and builds in the OpenShift explorer today, I believe we need to make them more distinguishable. > I propose we simply add the Pod/Build label like: > !http://content.screencast.com/users/fbricon/folders/Jing/media/22e3242c-e97b-4b06-8451-85d7948c0281/00000376.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22062) OpenShift Explorer : Make Pod/Build distinction more explicit

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22062: ------------------------------------- Summary: OpenShift Explorer : Make Pod/Build distinction more explicit Key: JBIDE-22062 URL: https://issues.jboss.org/browse/JBIDE-22062 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.3.1.CR1, 4.4.0.Alpha1 After witnessing a new user struggling with pods and builds in the OpenShift explorer today, I believe we need to make them more distinguishable. I propose we simply add the Pod/Build label like: !http://content.screencast.com/users/fbricon/folders/Jing/media/22e3242c-e97b-4b06-8451-85d7948c0281/00000376.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21964) OpenShift Explorer : Make Pod/Build distinction more explicit

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21964?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21964. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B260. > OpenShift Explorer : Make Pod/Build distinction more explicit > ------------------------------------------------------------- > > Key: JBIDE-21964 > URL: https://issues.jboss.org/browse/JBIDE-21964 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: ux > Fix For: 4.3.1.CR1 > > > After witnessing a new user struggling with pods and builds in the OpenShift explorer today, I believe we need to make them more distinguishable. > I propose we simply add the Pod/Build label like: > !http://content.screencast.com/users/fbricon/folders/Jing/media/22e3242c-e97b-4b06-8451-85d7948c0281/00000376.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22062) OpenShift Explorer : Make Pod/Build distinction more explicit

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22062?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-22062. ----------------------------------- Resolution: Done > OpenShift Explorer : Make Pod/Build distinction more explicit > ------------------------------------------------------------- > > Key: JBIDE-22062 > URL: https://issues.jboss.org/browse/JBIDE-22062 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: ux > Fix For: 4.4.0.Alpha1 > > > After witnessing a new user struggling with pods and builds in the OpenShift explorer today, I believe we need to make them more distinguishable. > I propose we simply add the Pod/Build label like: > !http://content.screencast.com/users/fbricon/folders/Jing/media/22e3242c-e97b-4b06-8451-85d7948c0281/00000376.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21964) OpenShift Explorer : Make Pod/Build distinction more explicit

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21964?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21964: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > OpenShift Explorer : Make Pod/Build distinction more explicit > ------------------------------------------------------------- > > Key: JBIDE-21964 > URL: https://issues.jboss.org/browse/JBIDE-21964 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: ux > Fix For: 4.3.1.CR1 > > > After witnessing a new user struggling with pods and builds in the OpenShift explorer today, I believe we need to make them more distinguishable. > I propose we simply add the Pod/Build label like: > !http://content.screencast.com/users/fbricon/folders/Jing/media/22e3242c-e97b-4b06-8451-85d7948c0281/00000376.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-22004: ------------------------------------------- {quote} end up claiming every folder with a VagrantFile in it is a cdk, because there's no real way to parse the VagrantFile to determine if it's actually referencing the CDK or not. {quote} Sure, but what if the CDK Vagrantfile would define some variable/value in its config. The value would be irrelevant really for the actual Vagrant config, but you could parse/grep for this value and if it exist consider this Vagrant setup as a CDK. The problem with the marker file is how to get it there. ATM, the CDK ships a zip bundle which contains a _Vagrantfile_ which you would need to copy into an empty directory. We could add the marker file to the zip bundle and document that the user should copy this file as well. However, that is error prone. Also in the hopefully not so long future, would would be able to create an initial Vagrant setup for the CDK by just typing {{vagrant init cdk}}. This would create an "empty" Vagrantfile just referencing the right box file. The actual default configuration would then be in the _Vagrantfile_ of the box file. How would we deal with the marker file then? I guess the "empty" config file might be problematic for my proposed solution for parsing for something in the _Vagrantfile_ as well. Another idea would be to add something to the default Vagrantfile which creates the .cdk file. After all the _Vagrantfile_ is plain Ruby!? Either way, just adding the marker file to the zip bundle of the CDK won't buy us much in the long run. We need different solution. > Runtime detection unable to detect CDK > -------------------------------------- > > Key: JBIDE-22004 > URL: https://issues.jboss.org/browse/JBIDE-22004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Hardy Ferentschik > Fix For: 4.4.x > > > Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it. > Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK? -- 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 April 2016