September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23272) Make target platform update process better

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23272?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23272: ---------------------------------- Assignee: Nick Boldt > Make target platform update process better > ------------------------------------------ > > Key: JBIDE-23272 > URL: https://issues.jboss.org/browse/JBIDE-23272 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Epic to collect the issues related to TP maintenance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23272) Make target platform update process better

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23272?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23272: ------------------------------- Fix Version/s: 4.4.2.AM2 > Make target platform update process better > ------------------------------------------ > > Key: JBIDE-23272 > URL: https://issues.jboss.org/browse/JBIDE-23272 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Epic to collect the issues related to TP maintenance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22602) Check if org.eclipse.core.runtime.compatibility.auth is needed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22602?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22602: ------------------------------- Parent: (was: JBIDE-22581) Issue Type: Feature Request (was: Sub-task) > Check if org.eclipse.core.runtime.compatibility.auth is needed > -------------------------------------------------------------- > > Key: JBIDE-22602 > URL: https://issues.jboss.org/browse/JBIDE-22602 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Fix For: 4.4.x > > > We removed org.eclipse.core.runtime.compatibility in JBIDE-21382 . But I noticed that we still have org.eclipse.core.runtime.compatibility.auth in the TP (and devstudio installation). > Do we need it? Shouldn't it be removed also? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22620) remove duplicate entries from target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22620?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22620: ------------------------------- Parent: (was: JBIDE-22581) Issue Type: Feature Request (was: Sub-task) > remove duplicate entries from target platforms > ---------------------------------------------- > > Key: JBIDE-22620 > URL: https://issues.jboss.org/browse/JBIDE-22620 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Fix For: 4.4.x > > > Current 4.60.0.Final TP contains duplicates of these IUs: > * org.eclipse.m2e.model.edit > * org.eclipse.egit.ui.smartimport > * ...others? > Duplication should be avoided. See also JBIDE-22611. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23272) Make target platform update process better

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23272: ---------------------------------- Summary: Make target platform update process better Key: JBIDE-23272 URL: https://issues.jboss.org/browse/JBIDE-23272 Project: Tools (JBoss Tools) Issue Type: Epic Components: target-platform Affects Versions: 4.4.2.AM2 Reporter: Nick Boldt Epic to collect the issues related to TP maintenance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present

by Rick Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ] Rick Wagner commented on JBDS-4065: ----------------------------------- Hi Denis, Thanks for that idea. Yes, I did keep the workspace. I'll try another install, after wiping out the workspace.... Rick > DevStudio 1.1 Installer unfriendly when 1.0 present > --------------------------------------------------- > > Key: JBDS-4065 > URL: https://issues.jboss.org/browse/JBDS-4065 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 10, DevSuite Installer 1.0 had been run > Reporter: Rick Wagner > Assignee: Rob Stryker > > When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK. > Observations: > - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned). > - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory. > - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is? > - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup. > - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22719) JavaModelException below DependencyCache.getDependentTypes (thrown in JavaElement.newJavaModelException)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22719?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-22719: ---------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > JavaModelException below DependencyCache.getDependentTypes (thrown in JavaElement.newJavaModelException) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22719 > URL: https://issues.jboss.org/browse/JBIDE-22719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: ticket-monster does not exist > {noformat} > org.eclipse.jdt.core.JavaModelException: ticket-monster does not exist > at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566) > at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1642) > at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2329) > at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2339) > at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1357) > at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1264) > at org.jboss.tools.arquillian.core.internal.dependencies.DependencyCache.getDependentTypes(DependencyCache.java:116) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder$1.visit(ArquillianBuilder.java:174) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:63) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:47) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:128) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 | > | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.100.Final-v20160610-0313-B2 | > Operating Systems: > | Linux | 3.16.0 | 4.6.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5741db16e4b0138d62...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22718) NullPointerException in HIDDEN

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22718?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-22718: ---------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > NullPointerException in HIDDEN > ------------------------------ > > Key: JBIDE-22718 > URL: https://issues.jboss.org/browse/JBIDE-22718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: > {noformat} > java.lang.NullPointerException: null > at HIDDEN.HIDDEN(HIDDEN:-1) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.addContainerProperties(ArquillianUIUtil.java:581) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:507) > at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:644) > at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.activated(AbstractLaunchConfigurationTab.java:411) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleTabSelected(LaunchConfigurationTabGroupViewer.java:1365) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$6.widgetSelected(LaunchConfigurationTabGroupViewer.java:377) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 | > Operating Systems: > | Windows | 6.3.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57344b2ee4b0138d62...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-389) TypeScript debugging [EBZ#487465]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-389?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-389: ------------------------------- Assignee: Victor Rubezhny > TypeScript debugging [EBZ#487465] > --------------------------------- > > Key: ERT-389 > URL: https://issues.jboss.org/browse/ERT-389 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: Debug, bzira > > I'm developping a TypeScript plugins based on JSDT & tsserver https://github.com/angelozerr/typescript.java and it should be very cool if JSDT debugger could debug TypeScript (by using source map). > If you are interested to work together about integration TypeScript (with JSDT), I have created an issue at https://github.com/angelozerr/typescript.java/issues/2. > Please note that TypEcs support debugging with Eclipse https://github.com/axmor/typecs/tree/master/src/com.axmor.eclipse.typescr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-389) TypeScript debugging [EBZ#487465]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-389?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-389: ---------------------------- Sprint: devex #121 October 2016 > TypeScript debugging [EBZ#487465] > --------------------------------- > > Key: ERT-389 > URL: https://issues.jboss.org/browse/ERT-389 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: Debug, bzira > > I'm developping a TypeScript plugins based on JSDT & tsserver https://github.com/angelozerr/typescript.java and it should be very cool if JSDT debugger could debug TypeScript (by using source map). > If you are interested to work together about integration TypeScript (with JSDT), I have created an issue at https://github.com/angelozerr/typescript.java/issues/2. > Please note that TypEcs support debugging with Eclipse https://github.com/axmor/typecs/tree/master/src/com.axmor.eclipse.typescr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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