[JBoss JIRA] (ERT-47) Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine [EBZ#486061]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-47?page=com.atlassian.jira.plugin.sys... ]
Ilya Buziuk commented on ERT-47:
--------------------------------
[~dgolovin], After investigating both JSDT & Chromium breakpoint model !breakpoints.png|thumbnail! I have figured out that using correct annotation id is not the only thing that should be changed to make it work. The main action happens in *BreakpointSynchronizer* which use *ChromiumBreakpointAdapter* - https://github.com/ChromeDevTools/cdt-java/blob/master/plugins/org.chromi... for breakpoint sync
So, if the JSDT breakpoint would be created with the correct Marker attributes mapping will not work - in order to make it work adapter should recognize and process JSDT breakpoint correctly. The main problem is that many things are coupled to ChromiumLineBreakpoint class directly, so it seems that the architecture should be changed to make those two work / sync correctly.
> 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
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
> Attachments: breakpoints.png
>
>
> 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)
8 years, 3 months
[JBoss JIRA] (JBTIS-564) Cannot install Fuse / SwitchYard tooling in offline mode
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-564?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-564:
----------------------------------
*Reason:* Move dependencies for an offline build out of the devstudio site-ea category.xml and into the jBTIS TP
*Project page/sources:*
*Version:* 4.3.1.Beta1b-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* JBDSIS
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
> org.eclipse.rse.dstore.feature.group [3.7.0.201505221634]
> org.eclipse.rse.doc.user [3.4.100.201403101646]
> org.eclipse.rse.connectorservice.local [2.1.400.201403100950]
> org.eclipse.zest.feature.group [1.6.1.201508170204]
> org.eclipse.rse.services [3.3.0.201403100950]
> org.eclipse.rse.subsystems.processes.dstore [2.1.400.201403100950]
> org.eclipse.rse.useractions.feature.group [3.7.0.201505221634]
> org.eclipse.dstore.core [3.4.0.201501311530]
> org.eclipse.rse.dstore.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.core.feature.group [3.7.0.201505221634]
> org.eclipse.rse.subsystems.terminals.ssh [1.0.200.201411271155]
> org.eclipse.rse.importexport [1.2.300.201403100950]
> org.eclipse.rse.processes.ui [3.0.400.201403100950]
> org.eclipse.rse.subsystems.files.dstore [2.1.300.201403100950]
> org.eclipse.rse.connectorservice.ssh [2.1.300.201505220524]
> org.eclipse.rse.core.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.telnet.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.useractions.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.connectorservice.dstore [3.1.301.201403100950]
> org.eclipse.dstore.extra [2.1.400.201403100950]
> org.eclipse.rse.core [3.3.100.201407181907]
> org.eclipse.rse.services.local [2.2.0.201502030655]
> org.eclipse.rse.subsystems.processes.core [3.1.300.201403100950]
> org.eclipse.rse.ftp.feature.group [3.7.0.201505221634]
> org.eclipse.rse.ftp.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.feature.group [3.7.0.201505221634]
> org.eclipse.rse [3.5.0.201403100950]
> org.eclipse.rse.ui [3.3.100.201503112018]
> org.eclipse.rse.subsystems.files.core [3.3.1.201403100950]
> org.eclipse.rse.files.ui [3.2.200.201502052140]
> org.eclipse.rse.subsystems.shells.local [2.1.400.201403100950]
> org.eclipse.rse.subsystems.shells.dstore [2.1.400.201403100950]
> org.eclipse.rse.subsystems.shells.telnet [1.2.300.201403100950]
> org.eclipse.rse.telnet.feature.group [3.7.0.201505221634]
> org.eclipse.rse.subsystems.processes.shell.linux [1.1.400.201403100950]
> org.eclipse.rse.subsystems.files.local [2.1.300.201403251512]
> org.eclipse.rse.terminals.feature.jar [3.8.0.201505221634]
> org.eclipse.rse.subsystems.shells.ssh [2.1.400.201403100950]
> org.eclipse.zest.core [1.5.201.201508170204]
> org.eclipse.rse.dstore.security [3.0.400.201403100950]
> org.eclipse.rse.subsystems.files.ftp [2.2.0.201403100950]
> org.eclipse.rse.local.feature.group [3.7.0.201505221634]
> org.eclipse.zest.layouts [1.1.200.201508170204]
> org.eclipse.rse.ssh.feature.group [3.7.0.201505221634]
> org.eclipse.rse.subsystems.files.ssh [2.1.300.201403100950]
> org.eclipse.rse.terminals.ui [1.3.0.201504210807]
> org.eclipse.zest.feature.jar [1.6.1.201508170204]
> org.eclipse.rse.services.files.ftp [3.0.500.201403100950]
> org.eclipse.rse.subsystems.processes.local [2.1.400.201403100950]
> org.eclipse.rse.subsystems.terminals.core [1.0.300.201411271155]
> org.eclipse.draw2d.feature.jar [3.10.1.201508170204]
> org.eclipse.rse.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.local.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.shells.ui [3.0.500.201403271554]
> org.eclipse.draw2d.feature.group [3.10.1.201508170204]
> org.eclipse.rse.useractions [1.1.500.201403100950]
> org.eclipse.rse.services.ssh [3.2.100.201403281521]
> org.eclipse.rse.terminals.feature.group [3.8.0.201505221634]
> org.eclipse.rse.connectorservice.telnet [1.2.300.201505220524]
> org.apache.commons.net [3.2.0.v201305141515]
> org.eclipse.rse.services.telnet [2.0.400.201403100950]
> org.eclipse.rse.ssh.feature.jar [3.7.0.201505221634]
> org.eclipse.rse.efs.ui [2.1.400.201403100950]
> org.eclipse.rse.efs [2.1.401.201503171741]
> org.eclipse.rse.services.dstore [3.3.0.201406041609]
> org.eclipse.rse.subsystems.shells.core [3.1.300.201403271554]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 66 unique IUs
{code}
> Cannot install Fuse / SwitchYard tooling in offline mode
> --------------------------------------------------------
>
> Key: JBTIS-564
> URL: https://issues.jboss.org/browse/JBTIS-564
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.Beta1
> Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1a EA Zip (md5 6ab445b312d39c451802232c5a54846b)
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Critical
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645)
> Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645)
> To: org.switchyard.tools.feature.feature.group 0.0.0
> {code}
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731)
> Missing requirement: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) requires 'org.eclipse.zest.core 0.0.0' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21789:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
Assignee: Andre Dietisheim
Resolution: Done
Applied in master / 4.3.x
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: openshift-3-connections-listed.png
>
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be.
> !openshift-3-connections-listed.png!
> If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21789:
--------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: openshift-3-connections-listed.png
>
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be.
> !openshift-3-connections-listed.png!
> If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21776:
-------------------------------------
+1 on the validation bits, As for the image pull, [~jcantrill] is working on getting the image metadata available without needing a pull, so I'd wait to see if that works fully.
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21788) builds for master and jbosstools-4.3.x are failing due to typo in parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21788?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21788:
-------------------------------
Summary: builds for master and jbosstools-4.3.x are failing due to typo in parent pom (was: Jenkins: builds for master and jbosstools-4.3.x are failing)
> builds for master and jbosstools-4.3.x are failing due to typo in parent pom
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21788
> URL: https://issues.jboss.org/browse/JBIDE-21788
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Nick Boldt
> Priority: Critical
> Labels: build, jenkins
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> Both jenkins builds for [jbosstools-4.3.x|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbo...] and [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490)
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (JBIDE-21788) Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21788?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-21788.
--------------------------------
Fix Version/s: 4.3.1.CR1
4.4.0.Alpha1
Resolution: Done
Typo introduced into parent pom via changes for JBIDE-21657. Should be fixed now. Jobs kicked in sequence.
(You should have been able to reproduce this locally by pulling the latest parent pom, or building the latest parent pom locally; but you'd only see the error if you attempted to do a `mvn deploy -Pdeploy-to-jboss.org`)
> Jenkins: builds for master and jbosstools-4.3.x are failing for openshift
> -------------------------------------------------------------------------
>
> Key: JBIDE-21788
> URL: https://issues.jboss.org/browse/JBIDE-21788
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Nick Boldt
> Priority: Critical
> Labels: build, jenkins
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> Both jenkins builds for [jbosstools-4.3.x|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbo...] and [master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-op...] are currently failing for openshift. I cant reproduce it locally, the error looks like some configuration error
> {code}
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:exec (deploy-snapshot-build) on project openshift.site: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Misconfigured argument (8), value is null. Set the argument to an empty value if this is the required behaviour.
> at org.codehaus.mojo.exec.ExecMojo.handleArguments(ExecMojo.java:490)
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:250)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months