August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1119) Update jbosstools-bpel to oxygen - 1.4.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1119?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1119. ------------------------------------ Resolution: Done Hey [~pleacu], thank you for clarification > Update jbosstools-bpel to oxygen - 1.4.0 > ---------------------------------------- > > Key: JBTIS-1119 > URL: https://issues.jboss.org/browse/JBTIS-1119 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPEL > Affects Versions: 4.5.0.AM1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.5.0.AM1-TP > > > Bump the version of jbosstools-bpel to 1.4.0 > Pick up 1.4.0 from download.eclipse.org -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24790) Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24790?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24790: ------------------------------------- Attachment: screenshot-1.png > Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24790 > URL: https://issues.jboss.org/browse/JBIDE-24790 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: screenshot-1.png > > > When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24790) Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24790?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24790: ------------------------------------- Description: When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes). Furthermore the text field and browse button are not properly aligned with the right border, there's a gap. !screenshot-1.png! was:When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes) > Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24790 > URL: https://issues.jboss.org/browse/JBIDE-24790 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: screenshot-1.png > > > When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes). > Furthermore the text field and browse button are not properly aligned with the right border, there's a gap. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24682: --------------------------------------- I will verify once more with the newest CDK build that will be available on Friday with devstudio build after CF. > Reflect changes in minishift's version command > ---------------------------------------------- > > Key: JBIDE-24682 > URL: https://issues.jboss.org/browse/JBIDE-24682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.0.Final > > > Due to changes in upstream project the 'minishift version' command returns different lines. > CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: > {code} > Minishift version: 1.0.0+4f8cb6d > CDK Version: 3.0.0-2 > {code} > vs. > CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: > {code} > minishift v1.2.0+001371f > CDK Version:3.0.0-13072017-1 > {code} > And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". > We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1119) Update jbosstools-bpel to oxygen - 1.4.0

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1119?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1119: ----------------------------------- Hey [~apodhrad] - JBossTools BPEL is version 1.4.0 . It is picking up Eclipse BPEL 1.1.1.Final. I will rebuild JBossTools BPEl 1.4.0.Final when the JBTIS TP is .Final > Update jbosstools-bpel to oxygen - 1.4.0 > ---------------------------------------- > > Key: JBTIS-1119 > URL: https://issues.jboss.org/browse/JBTIS-1119 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPEL > Affects Versions: 4.5.0.AM1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.5.0.AM1-TP > > > Bump the version of jbosstools-bpel to 1.4.0 > Pick up 1.4.0 from download.eclipse.org -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24296) Create Jenkins job for testing Docker with tests from upstream

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24296?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24296. --------------------------------- Resolution: Done Job is working: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/docker.i... > Create Jenkins job for testing Docker with tests from upstream > -------------------------------------------------------------- > > Key: JBIDE-24296 > URL: https://issues.jboss.org/browse/JBIDE-24296 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.4.4.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.Final > > > It needs to create new profile in pom in upstream. > Bugzilla with profile: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=520394 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24447 at 8/2/17 10:05 AM: ---------------------------------------------------------------- I have tested this features on devstudio: Version: 11.0.0.GA Build id: GA-v20170731-0116-B659 What I got... When I start devstudio with clean workspace, no runtime detection dialog is shown (Searcing new runtimes...) and when I open Servers View, I can see there is a CDK 3 server adapter! (It is called "Container Development Environment 3") and when I open the adapter, I have Minishift Home set to path that can be seen in pic (not important): !cdk2_x_RD.png|thumbnail! What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected). So, is it place for reporting new issue? I must say this situation might be result of me having installed multiple milestones of devstudios that I tested during past months or changes I made to environment, etc. Also, If I rename the cdk folder to something else, It starts working as can be read below. But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got: !cdk3_minishift_home.png|thumbnail! which lead to cdk runtime file that was set via MINSIHFT_HOME env. var. So it is working in this case. Just one thing. The Adapter is called "Container Development Environment 3", which does not happen when you create server adapter manually via New Server. It should be called the same, right? was (Author: odockal): I have tested this features on devstudio: Version: 11.0.0.GA Build id: GA-v20170731-0116-B659 What I got... When I start devstudio with clean workspace, no runtime detection dialog is shown (Searcing new runtimes...) and when I open Servers View, I can see there is a CDK 3 server adapter! (It is called "Container Development Environment 3") and when I open the adapter, I have Minishift Home set to path that can be seen in pic (not important): !cdk2_x_RD.png|thumbnail! What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected). So, is it place for reporting new issue? I must say this situation might be result of me having installed multiple milestones of devstudios that I tested during past months or changes I made to environment, etc. Also, If I rename the cdk folder to something else, It starts working as can be read below. But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got: !cdk3_minishift_home.png|thumbnail! which lead to cdk runtime file that was set via MINSIHFT_HOME env. var. So it is working in this case. > Look for minishift configuration in MINISHIFT_HOME > -------------------------------------------------- > > Key: JBIDE-24447 > URL: https://issues.jboss.org/browse/JBIDE-24447 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.4.4.Final > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: cdk2_x_RD.png, cdk3_minishift_home.png > > > One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift > It would be nice if runtime detection looked there if the variable is configured. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23489 at 8/2/17 10:04 AM: ------------------------------------------------------------- I wonder if there is a way to get the scl enabled for the spawned surefire process... was (Author: nickboldt): Have you tried enabling the scl? {code} # rm -fr ~/.eclipse scl enable rh-eclipse47 bash cd /opt/rh/rh-eclipse47/root/usr/lib/eclipse/ d=`date +%Y%m%d-%H%M` #then run eclipse in strict mode ./eclipse -consolelog -console -debug -data /tmp/wksp-${d} \ -clean -vmargs -Dosgi.resolver.usesMode=strict | tee \ -a /tmp/rh-eclipse47-devstudio$(cat .pkgs/Devstudio).log.${d}_strict.txt # or in non-strict mode ./eclipse -consolelog -console -debug -data /tmp/wksp-${d} \ -clean | tee \ -a /tmp/rh-eclipse47-devstudio$(cat .pkgs/Devstudio).log.${d}.txt {code} > Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm > ------------------------------------------------------------------------------ > > Key: JBIDE-23489 > URL: https://issues.jboss.org/browse/JBIDE-23489 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests, qa > Affects Versions: 4.4.2.AM3 > Reporter: Pavol Srna > Assignee: Lukáš Valach > Fix For: 4.5.x > > Attachments: FreeMarket_rhscl_enabled.log, Freemarker_testRuntime_p2Installed.log > > > We need to find a way how to run automated tests agains devstudio rpm. > I've tried the following paths: > 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/ > 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 > But none of the above works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23489: ------------------------------------ Have you tried enabling the scl? {code} # rm -fr ~/.eclipse scl enable rh-eclipse47 bash cd /opt/rh/rh-eclipse47/root/usr/lib/eclipse/ d=`date +%Y%m%d-%H%M` #then run eclipse in strict mode ./eclipse -consolelog -console -debug -data /tmp/wksp-${d} \ -clean -vmargs -Dosgi.resolver.usesMode=strict | tee \ -a /tmp/rh-eclipse47-devstudio$(cat .pkgs/Devstudio).log.${d}_strict.txt # or in non-strict mode ./eclipse -consolelog -console -debug -data /tmp/wksp-${d} \ -clean | tee \ -a /tmp/rh-eclipse47-devstudio$(cat .pkgs/Devstudio).log.${d}.txt {code} > Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm > ------------------------------------------------------------------------------ > > Key: JBIDE-23489 > URL: https://issues.jboss.org/browse/JBIDE-23489 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests, qa > Affects Versions: 4.4.2.AM3 > Reporter: Pavol Srna > Assignee: Lukáš Valach > Fix For: 4.5.x > > Attachments: FreeMarket_rhscl_enabled.log, Freemarker_testRuntime_p2Installed.log > > > We need to find a way how to run automated tests agains devstudio rpm. > I've tried the following paths: > 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/ > 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 > But none of the above works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24447 at 8/2/17 10:00 AM: ---------------------------------------------------------------- I have tested this features on devstudio: Version: 11.0.0.GA Build id: GA-v20170731-0116-B659 What I got... When I start devstudio with clean workspace, no runtime detection dialog is shown (Searcing new runtimes...) and when I open Servers View, I can see there is a CDK 3 server adapter! (It is called "Container Development Environment 3") and when I open the adapter, I have Minishift Home set to path that can be seen in pic (not important): !cdk2_x_RD.png|thumbnail! What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected). So, is it place for reporting new issue? I must say this situation might be result of me having installed multiple milestones of devstudios that I tested during past months or changes I made to environment, etc. Also, If I rename the cdk folder to something else, It starts working as can be read below. But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got: !cdk3_minishift_home.png|thumbnail! which lead to cdk runtime file that was set via MINSIHFT_HOME env. var. So it is working in this case. was (Author: odockal): I have tested this features on devstudio: Version: 11.0.0.GA Build id: GA-v20170731-0116-B659 What I got... When I start devstudio with clean workspace, no runtime detection dialog is shown (Searcing new runtimes...) and when I open Servers View, I can see there is a CDK 3 server adapter! (It is called "Container Development Environment 3") and when I open the adapter, I have Minishift Home set to path that can be seen in pic (not important): !cdk2_x_RD.png|thumbnail!. What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected). So, is it place for reporting new issue? I must say this situation might be result of me having installed multiple milestones of devstudios that I tested during past months or changes I made to environment, etc. Also, If I rename the cdk folder to something else, It starts working as can be read below. But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got: !cdk3_minishift_home.png|thumbnail! which lead to cdk runtime file that was set via MINSIHFT_HOME env. var. So it is working in this case. > Look for minishift configuration in MINISHIFT_HOME > -------------------------------------------------- > > Key: JBIDE-24447 > URL: https://issues.jboss.org/browse/JBIDE-24447 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.4.4.Final > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: cdk2_x_RD.png, cdk3_minishift_home.png > > > One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift > It would be nice if runtime detection looked there if the variable is configured. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 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 August 2017