August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22243: ------------------------------------------ [~jcantrill] ok, unassiged it. > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.4.2.AM1 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23059) Create and use ServiceLookup.getDefault() function

by Koen Aers (JIRA)

Koen Aers created JBIDE-23059: --------------------------------- Summary: Create and use ServiceLookup.getDefault() function Key: JBIDE-23059 URL: https://issues.jboss.org/browse/JBIDE-23059 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.1.AM3 Reporter: Koen Aers For now this function will return the hibernate service with the highest version number. Maybe later, this choice needs to be refined (e.g. the highest stable version). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23059) Create and use ServiceLookup.getDefault() function

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23059?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23059: --------------------------------- Assignee: Koen Aers > Create and use ServiceLookup.getDefault() function > --------------------------------------------------- > > Key: JBIDE-23059 > URL: https://issues.jboss.org/browse/JBIDE-23059 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.Final > > > For now this function will return the hibernate service with the highest version number. Maybe later, this choice needs to be refined (e.g. the highest stable version). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23059) Create and use ServiceLookup.getDefault() function

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23059?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23059: ------------------------------ Fix Version/s: 4.4.1.Final > Create and use ServiceLookup.getDefault() function > --------------------------------------------------- > > Key: JBIDE-23059 > URL: https://issues.jboss.org/browse/JBIDE-23059 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.Final > > > For now this function will return the hibernate service with the highest version number. Maybe later, this choice needs to be refined (e.g. the highest stable version). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-844) Update Target Platform: include m2e-wtp 1.2.2 in Mars TP

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-844?page=com.atlassian.jira.plugin.... ] Aurélien Pupier edited comment on JBTIS-844 at 8/30/16 11:23 AM: ----------------------------------------------------------------- [~apodhrad] Manually? the issue occurred something like 1 out of 10 times on my machine. You need to import the EAP Template of Fuse Tooling. you will have the stack which is in this comment if it still occurs: https://github.com/fusesource/fuseide/pull/654#issuecomment-242010459 was (Author: aurelien.pupier): [~apodhrad] Manually? the issue occurred something like 1 out of 10 times on my machine. You need to import the EAP Template of Fuse Tooling. > Update Target Platform: include m2e-wtp 1.2.2 in Mars TP > -------------------------------------------------------- > > Key: JBTIS-844 > URL: https://issues.jboss.org/browse/JBTIS-844 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Final > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > *Reason:* Have a fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=500197 which is blocking for [FUSETOOLS-1983] which is planned for Fuse Tooling 8.0.0 > *Project page/sources:* https://www.eclipse.org/m2e-wtp/ > *Version:* upgrade from 1.2.1 to 1.2.2 > *License and owner:* EPL, Eclipse > *Original p2 repo:* http://download.eclipse.org/m2e-wtp/releases/mars/ > *JBoss mirror:* Leave empty > *Include Sources:* included > *Affected JBoss Tools components:* Fuse Tooling > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* N/A > *non-p2 ids:* N/A -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-844) Update Target Platform: include m2e-wtp 1.2.2 in Mars TP

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-844?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBTIS-844: --------------------------------------- [~apodhrad] Manually? the issue occurred something like 1 out of 10 times on my machine. You need to import the EAP Template of Fuse Tooling. > Update Target Platform: include m2e-wtp 1.2.2 in Mars TP > -------------------------------------------------------- > > Key: JBTIS-844 > URL: https://issues.jboss.org/browse/JBTIS-844 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Final > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > *Reason:* Have a fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=500197 which is blocking for [FUSETOOLS-1983] which is planned for Fuse Tooling 8.0.0 > *Project page/sources:* https://www.eclipse.org/m2e-wtp/ > *Version:* upgrade from 1.2.1 to 1.2.2 > *License and owner:* EPL, Eclipse > *Original p2 repo:* http://download.eclipse.org/m2e-wtp/releases/mars/ > *JBoss mirror:* Leave empty > *Include Sources:* included > *Affected JBoss Tools components:* Fuse Tooling > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* N/A > *non-p2 ids:* N/A -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23058) VPE RefreshOptionsTest are failing from time to time on Jenkins

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23058?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23058: ------------------------------------- [~rawagner] I have also disabled *PreviewReloadTest* - do not know why but after disabling RefreshOptionsTest it starts to fail locally > VPE RefreshOptionsTest are failing from time to time on Jenkins > --------------------------------------------------------------- > > Key: JBIDE-23058 > URL: https://issues.jboss.org/browse/JBIDE-23058 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Ilya Buziuk > Assignee: Rastislav Wagner > Fix For: 4.4.2.AM1 > > > The following tests are failing from time to time on Jenkins (was not able to reproduce locally) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... > 1) on windows the following tests are failing from time to time: > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest > 2) on rhel7 the following tests are failing from time to time: > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest > org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest > Those tests were disabled as part of JBIDE-22884, need to figure out the reason of failures -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-844) Update Target Platform: include m2e-wtp 1.2.2 in Mars TP

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-844?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-844: ----------------------------------------- Hi [~aurelien.pupier], could you provide steps how we can verify the issue. please? Btw is this the only one bug fix whoch was added or are there more commits included? > Update Target Platform: include m2e-wtp 1.2.2 in Mars TP > -------------------------------------------------------- > > Key: JBTIS-844 > URL: https://issues.jboss.org/browse/JBTIS-844 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Final > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > *Reason:* Have a fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=500197 which is blocking for [FUSETOOLS-1983] which is planned for Fuse Tooling 8.0.0 > *Project page/sources:* https://www.eclipse.org/m2e-wtp/ > *Version:* upgrade from 1.2.1 to 1.2.2 > *License and owner:* EPL, Eclipse > *Original p2 repo:* http://download.eclipse.org/m2e-wtp/releases/mars/ > *JBoss mirror:* Leave empty > *Include Sources:* included > *Affected JBoss Tools components:* Fuse Tooling > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* N/A > *non-p2 ids:* N/A -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3841: ------------------------------------ Update: https://access.redhat.com/articles/2360571 Ensure that you are logged in using an Administrator account. The Installer adds drivers and changes environment variables and therefore requires Administrator permissions. Using a non-Administrator account and using the Run as Administrator option is not recommended. > Installer Sets Path for Wrong User > ---------------------------------- > > Key: JBDS-3841 > URL: https://issues.jboss.org/browse/JBDS-3841 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 > Reporter: Thomas Mäder > Assignee: Denis Golovin > Priority: Critical > Labels: user-docs > Fix For: 10.1.0.GA > > > When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Roland Grunberg edited comment on JBIDE-23039 at 8/30/16 10:30 AM: ------------------------------------------------------------------- I haven't had time to test this out, but here are a few suggestions : - Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag. - Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash', or 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"} was (Author: rgrunber): I haven't had time to test this out, but here are a few suggestions : - Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag. - Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"} > Need an interactive terminal that fits specific requirements > ------------------------------------------------------------ > > Key: JBIDE-23039 > URL: https://issues.jboss.org/browse/JBIDE-23039 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Attachments: vagranttty.png > > > CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. > 1) I must be able to get a Process or IProcess object when a command is run > 2) I must be able to get an event or know when the process terminates > 3) The terminal or console must be interactive and allow user input when prompted. > 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. > These three requirements thus far seem impossible to solve. Solutions that have been attempted are: > 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. > 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed: > a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input > b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen > 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. > Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. > Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? > No other obvious solutions have presented themselves in the past year. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016