July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3926) cache 7zip and resourcehacker so we don't have to download them for every build

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3926?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3926. ------------------------------- Fix Version/s: 10.1.0.AM2 (was: 10.1.0.AM3) Resolution: Done > cache 7zip and resourcehacker so we don't have to download them for every build > ------------------------------------------------------------------------------- > > Key: JBDS-3926 > URL: https://issues.jboss.org/browse/JBDS-3926 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Jan Richter > Fix For: 10.1.0.AM2 > > > We should cache 7zip and resourcehacker artifacts so we don't have to download them for every build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Sprint: devex #118 July 2016 (was: devex #117 July 2016) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM2 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3853) Installer: use node-rcedit instead of resourceHacker

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3853?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3853: -------------------------------- Fix Version/s: 10.1.0.AM2 (was: 10.1.0.AM3) > Installer: use node-rcedit instead of resourceHacker > ---------------------------------------------------- > > Key: JBDS-3853 > URL: https://issues.jboss.org/browse/JBDS-3853 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Jan Richter > Labels: havoc > Fix For: 10.1.0.AM2 > > > Installer's metadata and icon are changed by Gulp using Resource Hacker which requires that we manually pre-compile its configuration on every change in metadata (e.g. project version). > Change it to node-rcedit module (already used by electron-packager to do the same thing for binary inside self-extracting zip) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3822: -------------------------------- Sprint: (was: devex #117 July 2016) > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3961: -------------------------------- Fix Version/s: (was: 10.1.0.AM3) > CDK installation failed with progress bar stuck in 99% > ------------------------------------------------------ > > Key: JBDS-3961 > URL: https://issues.jboss.org/browse/JBDS-3961 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Environment: h3. Operating System: > Windows 10 Pro 64 Bit > h3. Devstudio version > Devstudio 1.0 GA > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Labels: cdk > Fix For: 10.1.0.AM2 > > Attachments: dev_studio_installation.PNG, install.log > > > I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations. > Observations: > CDK installation stuck in 99% with "failed" mark. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3822: ------------------------------------- The reason it is happening explained https://blogs.msdn.microsoft.com/astebner/2007/05/18/how-to-prevent-the-p.... Simple attempts to tweak manifest failed. > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22759) Error logged from Debug UI when EAP is started

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22759?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22759: ------------------------------------- Anyone know who's in charge of freemarker? This seems like their bug. > Error logged from Debug UI when EAP is started > ---------------------------------------------- > > Key: JBIDE-22759 > URL: https://issues.jboss.org/browse/JBIDE-22759 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker, server > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > > When I start EAP 7 in devstudio 10.0.1.AM2, I get two errors in the error log: > {code} > Error logged from Debug UI: > org.eclipse.core.runtime.CoreException: Plug-in org.jboss.ide.eclipse.freemarker was unable to load class org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker. > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.getLineTrackers(ProcessConsoleManager.java:281) > at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.connect(ConsoleLineNotifier.java:54) > at org.eclipse.ui.internal.console.ConsolePatternMatcher.addPatternMatchListener(ConsolePatternMatcher.java:232) > at org.eclipse.ui.console.TextConsole.addPatternMatchListener(TextConsole.java:409) > at org.eclipse.debug.internal.ui.views.console.ProcessConsole.<init>(ProcessConsole.java:228) > at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.launchChanged(ProcessConsoleManager.java:149) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:453) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043) > at org.eclipse.debug.core.Launch.fireChanged(Launch.java:393) > at org.eclipse.debug.core.Launch.addProcess(Launch.java:355) > at org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:126) > at org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:787) > at org.eclipse.jdt.launching.AbstractVMRunner.newProcess(AbstractVMRunner.java:170) > at org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:424) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractJavaServerLaunchDelegate.fireVMRunner(AbstractJavaServerLaunchDelegate.java:91) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.actualLaunch(AbstractStartJavaServerLaunchDelegate.java:95) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.launch(AbstractStartJavaServerLaunchDelegate.java:89) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.launch(LocalJBossLaunchController.java:94) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker cannot be found by org.jboss.ide.eclipse.freemarker_1.5.101.v20160714-1706 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) > ... 31 more > {code} > {code} > Plug-in org.jboss.ide.eclipse.freemarker was unable to load class org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker. > java.lang.ClassNotFoundException: org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker cannot be found by org.jboss.ide.eclipse.freemarker_1.5.101.v20160714-1706 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.getLineTrackers(ProcessConsoleManager.java:281) > at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.connect(ConsoleLineNotifier.java:54) > at org.eclipse.ui.internal.console.ConsolePatternMatcher.addPatternMatchListener(ConsolePatternMatcher.java:232) > at org.eclipse.ui.console.TextConsole.addPatternMatchListener(TextConsole.java:409) > at org.eclipse.debug.internal.ui.views.console.ProcessConsole.<init>(ProcessConsole.java:228) > at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.launchChanged(ProcessConsoleManager.java:149) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:453) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043) > at org.eclipse.debug.core.Launch.fireChanged(Launch.java:393) > at org.eclipse.debug.core.Launch.addProcess(Launch.java:355) > at org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:126) > at org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:787) > at org.eclipse.jdt.launching.AbstractVMRunner.newProcess(AbstractVMRunner.java:170) > at org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:424) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractJavaServerLaunchDelegate.fireVMRunner(AbstractJavaServerLaunchDelegate.java:91) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.actualLaunch(AbstractStartJavaServerLaunchDelegate.java:95) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.launch(AbstractStartJavaServerLaunchDelegate.java:89) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.launch(LocalJBossLaunchController.java:94) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > Note: This doesn't seem to have any effect on the functionality of the EAP server adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22664) Invalid registry URL when OS3 connection created by CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22664?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22664. --------------------------------- Resolution: Done Verified fixed by [~jeffmaury] > Invalid registry URL when OS3 connection created by CDK server > -------------------------------------------------------------- > > Key: JBIDE-22664 > URL: https://issues.jboss.org/browse/JBIDE-22664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: screenshot-1.png > > > When the OS3 connection is created when launching the CDK server, then the Docker registry URL is not valid (garbage characters at the end). This may be a Windows problem. The CDK version used what CDK 2.1RC5 (see [^screenshot-1.png]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-354) ASTParser does not parse expressions like `var a = b; ` correctly. [EBZ#498370]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-354: --------------------------------------- Summary: ASTParser does not parse expressions like `var a = b;` correctly. [EBZ#498370] Key: ERT-354 URL: https://issues.jboss.org/browse/ERT-354 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot The AST generated by org.eclipse.wst.jsdt.core.dom.ASTParser.createAST() is incorrect. For the expression `var a = b`, the AST does not recognize `a` as the variable, instead representing the statement as `var b` E.g. (Parentheses indicate the ASTNode's toString()) Statement: var b = 15; AST: [...] VariableDeclarationStatement (var b=20) InferredType VariableDeclarationFragment (b=20) SimpleName (b) NumberLiteral (20) Statement: var b = a; AST: [...] VariableDeclarationStatement (var a) InferredType VariableDeclarationFragment (a) SimpleName (a) The problem is not present for other node types (e.g. Assignment), not is it present when the right-hand-side contains an expression (e.g. `var c = b + a`) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22611: ------------------------------- Sprint: devex #118 July 2016 > target platform validation fails to detect duplicate IUs > -------------------------------------------------------- > > Key: JBIDE-22611 > URL: https://issues.jboss.org/browse/JBIDE-22611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM3 > > > Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example: > {code} > [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency. > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933) > [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022) > BUILD FAILED > {code} > But this is not the same error that Paul Leacu recently reported: > {code} > > [ERROR] Resolution failed: > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code} > So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is. > Either way, we need to make these problems more visible so they're caught sooner. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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