August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20512) Hitting enter next to an FTL constructs doesn't indent the line

by Daniel Dekany (JIRA)

Daniel Dekany created JBIDE-20512: ------------------------------------- Summary: Hitting enter next to an FTL constructs doesn't indent the line Key: JBIDE-20512 URL: https://issues.jboss.org/browse/JBIDE-20512 Project: Tools (JBoss Tools) Issue Type: Bug Components: freemarker Affects Versions: 4.3.0.Beta2 Reporter: Daniel Dekany When hitting enter when the cursor only has plain text next to it, the newly started line copies its indentation as expected. But if the cursor is directly before or after an FTL construct ({{$\{x\}}}, {{<#assign x = 1>}}, etc.) then after hitting enter the indentation will be 0. The most common case of running into this is hitting enter after an indented newly entered FTL construct, as then you will have to indent manually before you start typing the next line. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19944) JBoss Central URL's need rewiring since yahoo pipes is shutting down

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19944?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19944: --------------------------------------------- @fbricon what are the properties to use to test on JBDS 7,8 and 9 if they can read this feed ? Would like QE to go verify this since in JBDS 9 we only show the title where in previous versions we show actual content too so it needs more/additional info. > JBoss Central URL's need rewiring since yahoo pipes is shutting down > -------------------------------------------------------------------- > > Key: JBIDE-19944 > URL: https://issues.jboss.org/browse/JBIDE-19944 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.0.CR1 > > > " Yahoo Pipes: Pipes creation will not be supported as of Aug. 30 this year. Pipes infrastructure will run until Sept. 30, 2015 in read-only mode to help developers migrate their data. Please visit http://pipes.yahoo.com/pipes for additional details." > from http://yahoo.tumblr.com/post/120700756894/q2-2015-progress-report-on-our-... > Deadline is thus August 30th - we should before that have migrated all feedburners that pointed to our yahoo pipes to *something* else. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20450) Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20450?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-20450: ----------------------------------- Yes, [this commit | https://github.com/jbosstools/jbosstools-hibernate/commit/d86f88c10347817...] works around the problem. > Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test > ----------------------------------------------------------------------- > > Key: JBIDE-20450 > URL: https://issues.jboss.org/browse/JBIDE-20450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: testfailure > Fix For: 4.3.0.CR1 > > Attachments: org.hibernate.eclipse.console.test.log.txt > > > *Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate_... > Yet no test failures are logged, presumably because the test fails too early for logging to be done: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20450) Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20450?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-20450. ------------------------------- Resolution: Done > Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test > ----------------------------------------------------------------------- > > Key: JBIDE-20450 > URL: https://issues.jboss.org/browse/JBIDE-20450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: testfailure > Fix For: 4.3.0.CR1 > > Attachments: org.hibernate.eclipse.console.test.log.txt > > > *Test Failure(s) in JBIDE 4.3.0.CR1 for hibernate's eclipse.console.test:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate_... > Yet no test failures are logged, presumably because the test fails too early for logging to be done: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20493) jbossdevstudio.app keeps crashing while adding a direct-vm component

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20493?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-20493: ------------------------------------------- Unfortunately, I'm not able to reproduce this issue :( I tried it on macosx 10.10.5 with jdk1.8.0_45 and with your workspace > jbossdevstudio.app keeps crashing while adding a direct-vm component > -------------------------------------------------------------------- > > Key: JBIDE-20493 > URL: https://issues.jboss.org/browse/JBIDE-20493 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform, upstream > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio > Version: 8.1.0.GA > Build id: GA-v20150327-1349-B467 > Build date: 20150327-1349 > Reporter: Scott Stark > Assignee: Snjezana Peco > Attachments: hs_err_pid4526.log, hs_err_pid4624.log, hs_err_pid4862.log, jbosstools-diagnostics-20150823100812.zip, jbosstools-diagnostics-20150823125246.zip, workspace2.zip > > > The jbossdevstudio.app keeps crashing while using the visual designer to edit camel routes. This has happened 4 or 5 times in the past day. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Yue Wang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Yue Wang edited comment on JBIDE-20397 at 8/26/15 4:36 AM: ----------------------------------------------------------- [~jcantrill] Hi, I verified this issue(on JBoss OpenShift v3 Tools 3.0.0.CR1-v20150826-0235-B979), it's basically works fine. but there is a little usability issue: step to reproduce: 1. In port forwarding wizard, try to port forward with an occupied port(8080) In the port-forwarding table, it shows like : Name Local Port Remote Port Status 8080 8080 started In port-forwarding console is: Starting port-forwarding... 8080 -> 8080 done. 2.close the wizard, open it again In the port-forward table, it shows like : Name Local Port Remote Port Status 8080 8080 stopped what expected: In step1, there should be an error message to tell user the port is occupied and can't start the port forwarding. was (Author: yue.wang): @Jeff Cantrill Hi, I verified this issue(on JBoss OpenShift v3 Tools 3.0.0.CR1-v20150826-0235-B979), it's basically works fine. but there is a little usability issue: step to reproduce: 1. In port forwarding wizard, try to port forward with an occupied port(8080) In the port-forwarding table, it shows like : Name Local Port Remote Port Status 8080 8080 started In port-forwarding console is: Starting port-forwarding... 8080 -> 8080 done. 2.close the wizard, open it again In the port-forward table, it shows like : Name Local Port Remote Port Status 8080 8080 stopped what expected: In step1, there should be an error message to tell user the port is occupied and can't start the port forwarding. > [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Yue Wang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Yue Wang edited comment on JBIDE-20397 at 8/26/15 4:34 AM: ----------------------------------------------------------- @Jeff Cantrill Hi, I verified this issue(on JBoss OpenShift v3 Tools 3.0.0.CR1-v20150826-0235-B979), it's basically works fine. but there is a little usability issue: step to reproduce: 1. In port forwarding wizard, try to port forward with an occupied port(8080) In the port-forwarding table, it shows like : Name Local Port Remote Port Status 8080 8080 started In port-forwarding console is: Starting port-forwarding... 8080 -> 8080 done. 2.close the wizard, open it again In the port-forward table, it shows like : Name Local Port Remote Port Status 8080 8080 stopped what expected: In step1, there should be an error message to tell user the port is occupied and can't start the port forwarding. was (Author: yue.wang): Jeff Cantrill Hi, I verified this issue(on JBoss OpenShift v3 Tools 3.0.0.CR1-v20150826-0235-B979), it's basically works fine. but there is a little usability issue: step to reproduce: 1. In port forwarding wizard, try to port forward with an occupied port(8080) In the port-forwarding table, it shows like : Name Local Port Remote Port Status 8080 8080 started In port-forwarding console is: Starting port-forwarding... 8080 -> 8080 done. 2.close the wizard, open it again In the port-forward table, it shows like : Name Local Port Remote Port Status 8080 8080 stopped what expected: In step1, there should be an error message to tell user the port is occupied and can't start the port forwarding. > [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Yue Wang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Yue Wang commented on JBIDE-20397: ---------------------------------- Jeff Cantrill Hi, I verified this issue(on JBoss OpenShift v3 Tools 3.0.0.CR1-v20150826-0235-B979), it's basically works fine. but there is a little usability issue: step to reproduce: 1. In port forwarding wizard, try to port forward with an occupied port(8080) In the port-forwarding table, it shows like : Name Local Port Remote Port Status 8080 8080 started In port-forwarding console is: Starting port-forwarding... 8080 -> 8080 done. 2.close the wizard, open it again In the port-forward table, it shows like : Name Local Port Remote Port Status 8080 8080 stopped what expected: In step1, there should be an error message to tell user the port is occupied and can't start the port forwarding. > [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-664) JBDS-IS 8.0.3: Create Release Notes

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-664?page=com.atlassian.jira.plug... ] Andrej Podhradsky commented on TOOLSDOC-664: -------------------------------------------- Now, I don't have any objections ;-) > JBDS-IS 8.0.3: Create Release Notes > ----------------------------------- > > Key: TOOLSDOC-664 > URL: https://issues.jboss.org/browse/TOOLSDOC-664 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20331) install grinder fails due to oomph or beaker virt slaves?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-20331 at 8/26/15 3:58 AM: ----------------------------------------------------------------- Another issue is that the config "jbosstools_site_stream=${JOB_NAME#*_} # master or 4.3.mars" doesn't work as expected for matrix job, as it suffixed the parameters of the indivudual "cell" job. https://issues.jenkins-ci.org/browse/JENKINS-28176 To sum up current issues: # beaker/metacity # fuseqa/webkitgtk3 # oomph # wrong instruction in job config ("jbosstools_site_stream=${JOB_NAME#*_} ). Fixed with https://github.com/jbdevstudio/jbdevstudio-ci/commit/12b1034b0e5f3b30e368... was (Author: mickael_istria): Another issue is that the config "jbosstools_site_stream=${JOB_NAME#*_} # master or 4.3.mars" doesn't work as expected for matrix job, as it suffixed the parameters of the indivudual "cell" job. https://issues.jenkins-ci.org/browse/JENKINS-28176 To sum up current issues: # beaker/metacity # fuseqa/webkitgtk3 # oomph # wrong instruction in job config ("jbosstools_site_stream=${JOB_NAME#*_} # master or 4.3.mars"). Fixed with https://github.com/jbdevstudio/jbdevstudio-ci/commit/12b1034b0e5f3b30e368... > install grinder fails due to oomph or beaker virt slaves? > --------------------------------------------------------- > > Key: JBIDE-20331 > URL: https://issues.jboss.org/browse/JBIDE-20331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > Attachments: install-grinder-fail.txt, virt1-ftl.png, virt2-ftl.png > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull} > 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 2015