February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-35) Launch configuration for node.js applications [EBZ#484597]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-35?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-35: ---------------------------- Story Points: 25 > Launch configuration for node.js applications [EBZ#484597] > ----------------------------------------------------------- > > Key: ERT-35 > URL: https://issues.jboss.org/browse/ERT-35 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M7, Debug, bzira > Fix For: Neon (4.6) M7 > > > We need a launch configuration that can understand package.json file on a project and launch/debug a JS application on a local node.js instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-49) Launch Configuration for Browser based applications [EBZ#486066]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-49?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-49: ---------------------------- Story Points: 25 > Launch Configuration for Browser based applications [EBZ#486066] > ---------------------------------------------------------------- > > Key: ERT-49 > URL: https://issues.jboss.org/browse/ERT-49 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-48) Support Chromium based browser debugging [EBZ#486065]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-48?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-48: ---------------------------- Story Points: 50 > Support Chromium based browser debugging [EBZ#486065] > ----------------------------------------------------- > > Key: ERT-48 > URL: https://issues.jboss.org/browse/ERT-48 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > > JSDT Should support running Chromium based browser in debug mode and start debug session for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-3) Investigate defining browsers / runtimes to use for debugging [EBZ#359436]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-3?page=com.atlassian.jira.plugin.syst... ] Gorkem Ercan updated ERT-3: --------------------------- Story Points: 50 (was: 25) > Investigate defining browsers / runtimes to use for debugging [EBZ#359436] > -------------------------------------------------------------------------- > > Key: ERT-3 > URL: https://issues.jboss.org/browse/ERT-3 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, Debug, bzira > Fix For: Neon (4.6) M6 > > > Akin to JDT's notion of an installed JRE (EE), we should investigate being able to define browsers (Firefox et. al.) and runtimes (node.js, Rhino, etc) that can be used to run / debug with. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-45) Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-45?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-45: ---------------------------- Story Points: 25 > Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057] > -------------------------------------------------------------------------------- > > Key: ERT-45 > URL: https://issues.jboss.org/browse/ERT-45 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > > Chromium JavaScript Debugger by default expose scripts loaded in JavaScript VM through virtual file system. It looks like normal workspace project with name matches the launch configuration name. > All interactions with VM are done through actions available on files in that virtual system. > Ideally that virtual FS should not be exposed to user if project that targeted for debug is already presented in workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-47) Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine [EBZ#486061]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-47?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-47: ---------------------------- Story Points: 25 > Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine [EBZ#486061] > --------------------------------------------------------------------------------------- > > Key: ERT-47 > URL: https://issues.jboss.org/browse/ERT-47 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > > Current implementation in ChromeDevTools can map breakpoints from files in workspace to running VM. Problem is .js file editor from ChomeDevTools should be used to create breakpoints, because breakpoint annotation id used in mapping is different from breakpoint annotation id used in JSDT. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-3) Investigate defining browsers / runtimes to use for debugging [EBZ#359436]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-3?page=com.atlassian.jira.plugin.syst... ] Gorkem Ercan updated ERT-3: --------------------------- Story Points: 25 > Investigate defining browsers / runtimes to use for debugging [EBZ#359436] > -------------------------------------------------------------------------- > > Key: ERT-3 > URL: https://issues.jboss.org/browse/ERT-3 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, Debug, bzira > Fix For: Neon (4.6) M6 > > > Akin to JDT's notion of an installed JRE (EE), we should investigate being able to define browsers (Firefox et. al.) and runtimes (node.js, Rhino, etc) that can be used to run / debug with. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Omair Majid (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Omair Majid commented on JBDS-3586: ----------------------------------- It turned out to be a CRC error in a graphiti jar. If anyone has any experience with ensuring file uploads via a buckminster build don't get corrupted, please help out in the graphiti bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=486638 The graphiti developer is suggesting to wait for M5 - which goes out this friday and should (hopefully) fix the CRC mismatch issue. > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Priority: Critical > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21568) No new repository found when recognizing maven repo

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21568?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21568: ----------------------------------- Assignee: Snjezana Peco (was: Fred Bricon) Resolution: Done Applied in master and 4.3.x. Thanks [~snjeza] > No new repository found when recognizing maven repo > --------------------------------------------------- > > Key: JBIDE-21568 > URL: https://issues.jboss.org/browse/JBIDE-21568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.1.Beta2 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21617) Import wizard: Build config should be preselected if service in Explorer is selected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21617?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21617: ------------------------------------- Summary: Import wizard: Build config should be preselected if service in Explorer is selected (was: Build config should be preselected in Import application wizard if service in Explorer is selected) > Import wizard: Build config should be preselected if service in Explorer is selected > ------------------------------------------------------------------------------------ > > Key: JBIDE-21617 > URL: https://issues.jboss.org/browse/JBIDE-21617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: explorer, import_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > When I am trying to import an OpenShift application via context menu of a service the Import OpenShift application wizard is opened, but first project is preselected in the wizard. It would be nice, if appropriate build config would be preselected if I have a selected service in OpenShift epxlorer view and opening Import OpenShift application wizard via its context menu. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016