July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20301) Freemarker outline view is not updated when level of details changed in preferences

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20301?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20301: ---------------------------------- Fix Version/s: 4.3.x > Freemarker outline view is not updated when level of details changed in preferences > ----------------------------------------------------------------------------------- > > Key: JBIDE-20301 > URL: https://issues.jboss.org/browse/JBIDE-20301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.3.x > > > Outline for ftl file without functions and macros stays enpty even if level of details changed to Full in preferences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20301) Freemarker outline view is not updated when level of details changed in preferences

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-20301: ------------------------------------- Summary: Freemarker outline view is not updated when level of details changed in preferences Key: JBIDE-20301 URL: https://issues.jboss.org/browse/JBIDE-20301 Project: Tools (JBoss Tools) Issue Type: Bug Components: freemarker Affects Versions: 4.3.0.Beta2 Reporter: Denis Golovin Outline for ftl file without functions and macros stays enpty even if level of details changed to Full in preferences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20114) New server uses openshift.redhat.com host name in case OpenShift server adapter has been selected in tree

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20114?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20114. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.3.0.CR1 Resolution: Done I've made this change, because I got tired of seeing this jira. 1) The default host for jboss / wf / etc servers is now "localhost" 2) Whenever you select a server type in the new server wizard, it will ask to set the defaults... so.... 3) Clicking wf8, typing in a host of "myHost", and then clicking *again* on wf8 (or any other server type) will reset the host to "localhost" So basically, you cannot type a host and then choose your server type anymore. You now must choose your server type before you input your host. > New server uses openshift.redhat.com host name in case OpenShift server adapter has been selected in tree > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20114 > URL: https://issues.jboss.org/browse/JBIDE-20114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.3.0.CR1 > > > If in New server wizard in tree containing server types is selected at first OpenShift server adapter and then any server, host name stays openshift.redhat.com. If user is not careful enough, he does not have to notice this and his server won't start. Host name in wizard should change accordingly to used server (prefill localhost for servers). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20217) JDT Debug can not connect/list VM started with suspend=y

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20217?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20217. --------------------------------- Resolution: Done I've gotten it to actually show these processes now, but they obviously lack required information wrt name, args, port, etc. When right-clicking and selecting "connect debugger", rather than automatically connect a debugger, the dialog that allows you to choose from auto-discovered procersses will show up. You'll now see an option to manually set a specific port to debug rather than choose an auto-detected element from the list. Since this UI is approached without knowing a main class or args or port, in this specific usecase, all workspace projects will be added to the source path computation to allow for a most functional ootb experience. > JDT Debug can not connect/list VM started with suspend=y > -------------------------------------------------------- > > Key: JBIDE-20217 > URL: https://issues.jboss.org/browse/JBIDE-20217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Aslak Knutsen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.CR1 > > > Having a VM started with suspend=y cause the following error to be logged from https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... due to Exception thrown in ToolsCore.getJvmArgs > Seemingly JVMStat can not connect to a suspended VM. > {code} > eclipse.buildId=4.5.0.I20150603-2000 > java.version=1.8.0_45 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Command-line arguments: -os linux -ws gtk -arch x86_64 > org.jboss.tools.common.jdt.debug > Error > Wed Jul 08 17:16:00 CEST 2015 > {code} > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: sun.jvmstat.monitor.MonitorException: Could not synchronize with target > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) > at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) > at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) > at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) > at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) > ... 14 more > Root exception: > sun.jvmstat.monitor.MonitorException: Could not synchronize with target > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) > at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) > at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) > at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) > at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3484) Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3484?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3484: ----------------------------- Labels: respin-a (was: ) > Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3484 > URL: https://issues.jboss.org/browse/JBDS-3484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: javascript > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-a > Fix For: 9.0.0.Beta2 > > > Currently org.jboss.tools.jst.js.feature with bower integration available only from jbosstools aggregated p2 repository. > This is very desired feature for javascript development and should be included into into JBDS installer, BYOE feature and JBDS p2 repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to 0.10.0 release after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19963: ---------------------------------- Labels: new_and_noteworthy respin-a (was: new_and_noteworthy) > Switch Tern.java dependency version range to 0.10.0 release after code freeze > ----------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy, respin-a > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20299) JBDS central discovery site contains jbosstools-directory.xml/jbosstools-earlyaccess.properties; JBT EA site contains devstudio-directory.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20299?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20299. ------------------------------ Assignee: Nick Boldt Fix Version/s: 4.3.0.Beta2 Resolution: Done This turned out the be a bug when releasing to stage -- overlapping temp folders caused the snafu. Fixed in release guide. > JBDS central discovery site contains jbosstools-directory.xml/jbosstools-earlyaccess.properties; JBT EA site contains devstudio-directory.xml > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20299 > URL: https://issues.jboss.org/browse/JBIDE-20299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Beta2 > > > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > contains an extra jbosstools-directory.xml file (and an extra jbosstools-earlyaccess.properties file, too). > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 > [TXT] compositeContent.xml 17-Jul-2015 13:38 868 > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 > [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - > {code} > But the EA site does not: > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 1.1K > [TXT] compositeContent.xml 17-Jul-2015 13:38 1.1K > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [ ] devstudio-earlyaccess.properties 12-May-2015 23:22 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - {code} > So for some reason we're mixing JBT content into the JBDS Central Discovery site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to 0.10.0 release after code freeze

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19963: ------------------------------------ Too late! Beta2 is released to staging for QE. If this is really a blocker, we'll need to respin-a. Why does this dependency range NEED to be set? What's wrong with just bundle-version = 0.10.0 instead of [0.10.0.201506172156,0.10.0.201506172156] ? > Switch Tern.java dependency version range to 0.10.0 release after code freeze > ----------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20299) JBDS central discovery site contains jbosstools-directory.xml/jbosstools-earlyaccess.properties; JBT EA site contains devstudio-directory.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20299?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20299 at 7/17/15 2:46 PM: ------------------------------------------------------------- Similar problem, which I've had to *fix manually for now*, as the composite*.xml files were from JBDS Central Discovery for some reason. http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... {code} [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 [TXT] compositeContent.xml 17-Jul-2015 13:38 868 [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K [DIR] plugins/ 17-Jul-2015 13:38 - {code} yet the JBT Central Discovery site is fine. was (Author: nickboldt): Similar problem... http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-4.3.0... {code} [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 [TXT] compositeContent.xml 17-Jul-2015 13:38 868 [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K [DIR] plugins/ 17-Jul-2015 13:38 - {code} yet the JBT Central Discovery site is fine. > JBDS central discovery site contains jbosstools-directory.xml/jbosstools-earlyaccess.properties; JBT EA site contains devstudio-directory.xml > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20299 > URL: https://issues.jboss.org/browse/JBIDE-20299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Priority: Critical > > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > contains an extra jbosstools-directory.xml file (and an extra jbosstools-earlyaccess.properties file, too). > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 868 > [TXT] compositeContent.xml 17-Jul-2015 13:38 868 > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [TXT] jbosstools-directory.xml 17-Jul-2015 13:38 366 > [ ] jbosstools-earlyaccess.properties 16-Jul-2015 13:53 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - > {code} > But the EA site does not: > https://devstudio.redhat.com/9.0/staging/builds/devstudio-9.0.0.Beta2-bui... > {code} > [TXT] compositeArtifacts.xml 17-Jul-2015 13:38 1.1K > [TXT] compositeContent.xml 17-Jul-2015 13:38 1.1K > [TXT] devstudio-directory.xml 17-Jul-2015 13:38 364 > [ ] devstudio-earlyaccess.properties 12-May-2015 23:22 4.2K > [DIR] plugins/ 17-Jul-2015 13:38 - {code} > So for some reason we're mixing JBT content into the JBDS Central Discovery site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3484) Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3484?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3484: ----------------------------- CDW release: + (was: ?) > Include org.jboss.tools.jst.js.feature with bower integration into p2repository, installer and BYOE feature > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3484 > URL: https://issues.jboss.org/browse/JBDS-3484 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: javascript > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Currently org.jboss.tools.jst.js.feature with bower integration available only from jbosstools aggregated p2 repository. > This is very desired feature for javascript development and should be included into into JBDS installer, BYOE feature and JBDS p2 repository. -- 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 July 2015