August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3983: ----------------------------- > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3983: ----------------------------- > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3983: -------------------------------- > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3983: -------------------------------- > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3983: -------------------------------- > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3983: -------------------------------- > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22446: ------------------------------------ Coud we get a detail on the NPE ? is it in our rule or in the Maven plugin. I don't like the idea to get the rule in each individual POM as it is likely to fail one day or another > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.AM3 > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-820) Update SwitchYard tests to work with Integration Pack

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-820?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-820. ------------------------------ PR was pushed to master branch > Update SwitchYard tests to work with Integration Pack > ----------------------------------------------------- > > Key: JBTIS-820 > URL: https://issues.jboss.org/browse/JBTIS-820 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.3.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > Update SwitchYard tests to work with Integration Pack > * do not remove switchyard and kie boms > * add mvn repos for new Intagration Packs -- 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22759?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-22759. ------------------------------------ Resolution: Done > 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: Bug > Components: freemarker, server > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM3 > > > 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-22647) Update code to support openshift-restclient-java changes including auth context

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22647?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22647: --------------------------------------- [~jeffmaury] During implementation of this PR, I noticed there was a limit to the number of concurrent requests the client could make to a single host. I increased the number in addition to creating a new okhttpclient upon each call to watch, this is assuming I understand how the library works. The ClientBuilder increments the value where in the WatchClient is where the new okhttpclient is created. I would not think this is the issue. > Update code to support openshift-restclient-java changes including auth context > ------------------------------------------------------------------------------- > > Key: JBIDE-22647 > URL: https://issues.jboss.org/browse/JBIDE-22647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.1.AM3 > > -- 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 August 2016