December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20976) Create and use Neon M4 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20976: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-discovery/commit/3750aa93b7482d6..., https://github.com/jbosstools/jbosstools-target-platforms/pull/187, https://github.com/jbosstools/jbosstools-discovery/pull/323 (was: https://github.com/jbosstools/jbosstools-discovery/commit/3750aa93b7482d6...) PRs to move up to Neon M4: https://github.com/jbosstools/jbosstools-target-platforms/pull/187 https://github.com/jbosstools/jbosstools-discovery/pull/323 > Create and use Neon M4 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, p2diff.jbdevstudio_v2.txt, p2diff.jbosstools.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21359) Add builds tab for deployment view changes

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21359?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21359: --------------------------------------- [~fbricon] merged the dependency and created a WIP pull request for review. > Add builds tab for deployment view changes > ------------------------------------------ > > Key: JBIDE-21359 > URL: https://issues.jboss.org/browse/JBIDE-21359 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Add builds tab for deployment view changes > * List of builds for a deployment > * Individual build details > * Clone build > * Build logs -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21171) Need to remove bower / npm from jboss.tools.jsdt

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21171?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-21171: ------------------------------------- [~nickboldt], in the long run, yes. But for now we want just remove it > Need to remove bower / npm from jboss.tools.jsdt > ------------------------------------------------ > > Key: JBIDE-21171 > URL: https://issues.jboss.org/browse/JBIDE-21171 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Assuming that bower / npm were moved to eclipse jsdt - https://git.eclipse.org/r/#/c/61336/ > Need to perform a cleanup in jboss.tools.jst.jsdt repo and remove related plugins / tests / features > Bower is in eclipse upstream and we probably will need reflect it in new & noteworthy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21383) Content assist for facelet function does not work in an unclosed EL before next EL

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-21383: --------------------------------------------- Summary: Content assist for facelet function does not work in an unclosed EL before next EL Key: JBIDE-21383 URL: https://issues.jboss.org/browse/JBIDE-21383 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core, jsf Affects Versions: 4.4.0.Alpha1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.4.0.Alpha1 1. Add to page some facelet taglib with functions, let its namespace be 'p'. 2. Try content assist after ':' in {code} #{p: #{someBean} {code} It fails. 3. Close EL {code} #{p:} #{someBean} {code} Now, content assist works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21359) Add builds tab for deployment view changes

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21359?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21359: --------------------------------------- [~fbricon] https://github.com/jcantrill/openshift-restclient-java/tree/231_update_bu... and https://github.com/jcantrill/jbosstools-openshift/tree/21359_builds_tab for your review > Add builds tab for deployment view changes > ------------------------------------------ > > Key: JBIDE-21359 > URL: https://issues.jboss.org/browse/JBIDE-21359 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Add builds tab for deployment view changes > * List of builds for a deployment > * Individual build details > * Clone build > * Build logs -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21171) Need to remove bower / npm from jboss.tools.jsdt

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21171?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21171: ------------------------------------ Going to assume you want this feature [1] added to the 4.60.x TPs from this mirror [2]. [1] org.eclipse.wst.jsdt.nodejs.feature_1.0.0.v201512020037.jar [2] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... Going to further assume you want that feature added to the JBT/JBDS update sites INSTEAD of the one removed via the PRs above (org.jboss.tools.jst.js.feature), and that this new feature should also replace the removed one in the JBDS core feature.xml too. > Need to remove bower / npm from jboss.tools.jsdt > ------------------------------------------------ > > Key: JBIDE-21171 > URL: https://issues.jboss.org/browse/JBIDE-21171 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Assuming that bower / npm were moved to eclipse jsdt - https://git.eclipse.org/r/#/c/61336/ > Need to perform a cleanup in jboss.tools.jst.jsdt repo and remove related plugins / tests / features > Bower is in eclipse upstream and we probably will need reflect it in new & noteworthy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21358) Terminating application running in debug mode results in exception

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21358?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21358: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Terminating application running in debug mode results in exception > ------------------------------------------------------------------ > > Key: JBIDE-21358 > URL: https://issues.jboss.org/browse/JBIDE-21358 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, jmx > Affects Versions: 4.3.1.Beta1 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > {code} > org.jboss.tools.common.jdt.debug.tools.ToolsCoreException: > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:585) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) > 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.invokeGetMonitoredVm(Tools.java:583) > ... 9 more > Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found > at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68) > at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77) > at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67) > ... 13 more > Caused by: java.lang.IllegalArgumentException: Process not found > at sun.misc.Perf.attach(Native Method) > at sun.misc.Perf.attachImpl(Perf.java:270) > at sun.misc.Perf.attach(Perf.java:200) > at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64) > ... 16 more > {code} > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) > 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.invokeGetMonitoredVm(Tools.java:583) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found > at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84) > at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68) > at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77) > at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67) > ... 13 more > Caused by: java.lang.IllegalArgumentException: Process not found > at sun.misc.Perf.attach(Native Method) > at sun.misc.Perf.attachImpl(Perf.java:270) > at sun.misc.Perf.attach(Perf.java:200) > at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64) > ... 16 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21382) remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21382?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21382: ---------------------------------- Assignee: Alexey Kazakov > remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21382 > URL: https://issues.jboss.org/browse/JBIDE-21382 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.0.Alpha1 > > > org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 was removed from Neon as of M3. It is required by these IUs: > * o.j.t.common.model.ui, > * o.e.platform.feature, > * o.e.m2e.feature, > * o.e.datatools.oda.cshelp, > * o.aspectj.ajde, > * o.e.wst.xml.xpath.core, and > * o.e.birt.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21382) remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21382: ---------------------------------- Summary: remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3) Key: JBIDE-21382 URL: https://issues.jboss.org/browse/JBIDE-21382 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: common/jst/core Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 was removed from Neon as of M3. It is required by these IUs: * o.j.t.common.model.ui, * o.e.platform.feature, * o.e.m2e.feature, * o.e.datatools.oda.cshelp, * o.aspectj.ajde, * o.e.wst.xml.xpath.core, and * o.e.birt.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21309) install tests should perform installs on minimum and maximum TPs, and report on which there are failures

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21309?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21309. ------------------------------ Resolution: Done Got confirmation from Pascal Rapicault that there's currently no remediation available in the p2 director, so there's no way to set up headless jobs which can install Mars.1 deps into Mars.0. But as we have install-grinder, we can keep using that for remediated install scenarios. > install tests should perform installs on minimum and maximum TPs, and report on which there are failures > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21309 > URL: https://issues.jboss.org/browse/JBIDE-21309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Currently, we run the install tests on the maximum TP using the latest Eclipse JEE or Platform Binary. > If we can't do an install against Mars.0 (only Mars.1) due to the fact that the Mars.0 install requires remediation, we should have those tests to show the failure, and log that in the N&N. > Also, if install-grinder can support p2 remediation, that would be awesome too as we could verify that use case too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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