July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22643) Explorer: Connection error is shown as child of "Loading...", should replace it

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22643?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22643: ------------------------------------ Story Points: 12 > Explorer: Connection error is shown as child of "Loading...", should replace it > ------------------------------------------------------------------------------- > > Key: JBIDE-22643 > URL: https://issues.jboss.org/browse/JBIDE-22643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Fix For: 4.4.1.AM3 > > Attachments: token-error-shown-as-child.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22626: ------------------------------------ Story Points: 8 > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.AM3 > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22643) Explorer: Connection error is shown as child of "Loading...", should replace it

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22643?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22643: ------------------------------------ Sprint: devex #118 July 2016 > Explorer: Connection error is shown as child of "Loading...", should replace it > ------------------------------------------------------------------------------- > > Key: JBIDE-22643 > URL: https://issues.jboss.org/browse/JBIDE-22643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.AM3 > > Attachments: token-error-shown-as-child.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22643) Explorer: Connection error is shown as child of "Loading...", should replace it

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22643?page=com.atlassian.jira.plugi... ] Dmitry Bocharov reassigned JBIDE-22643: --------------------------------------- Assignee: Dmitry Bocharov > Explorer: Connection error is shown as child of "Loading...", should replace it > ------------------------------------------------------------------------------- > > Key: JBIDE-22643 > URL: https://issues.jboss.org/browse/JBIDE-22643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Fix For: 4.4.1.AM3 > > Attachments: token-error-shown-as-child.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22661) Docker registry URL not saved

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22661?page=com.atlassian.jira.plugi... ] Dmitry Bocharov closed JBIDE-22661. ----------------------------------- Assignee: Dmitry Bocharov Resolution: Duplicate Issue > Docker registry URL not saved > ----------------------------- > > Key: JBIDE-22661 > URL: https://issues.jboss.org/browse/JBIDE-22661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitry Bocharov > Priority: Critical > Fix For: 4.4.1.AM3 > > > ASSERT: create an OS3 connection without Docker registry URL > EXEC: go to Docker explorer, select an image and Deploy to Openshift > EXEC: select the OS3 connection and add the Docker registry URL and click Next > ASSERT: in the next page, select the Push Image to regsitry but the registry URL is not filled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22661) Docker registry URL not saved

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22661?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22661: ------------------------------------ Comment: was deleted (was: see PR for https://issues.jboss.org/browse/JBIDE-22594) > Docker registry URL not saved > ----------------------------- > > Key: JBIDE-22661 > URL: https://issues.jboss.org/browse/JBIDE-22661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Priority: Critical > Fix For: 4.4.1.AM3 > > > ASSERT: create an OS3 connection without Docker registry URL > EXEC: go to Docker explorer, select an image and Deploy to Openshift > EXEC: select the OS3 connection and add the Docker registry URL and click Next > ASSERT: in the next page, select the Push Image to regsitry but the registry URL is not filled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22626: ------------------------------------ Sprint: devex #118 July 2016 > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.AM3 > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Dmitry Bocharov reassigned JBIDE-22626: --------------------------------------- Assignee: Dmitry Bocharov > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.AM3 > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22759?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22759: --------------------------------------- [~rob.stryker], I thought it was ours? https://github.com/jbosstools/jbosstools-freemarker > 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-22765) In FTL file in editor are missing directives in code assistant

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22765?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-22765 at 7/25/16 7:03 AM: ---------------------------------------------------------------- Possible cause in [JBIDE-20386|https://issues.jboss.org/browse/JBIDE-20386]. was (Author: odockal): Duplicate of [JBIDE-20386|https://issues.jboss.org/browse/JBIDE-20386]. > In FTL file in editor are missing directives in code assistant > -------------------------------------------------------------- > > Key: JBIDE-22765 > URL: https://issues.jboss.org/browse/JBIDE-22765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160715-2233-B5663 > Build date: 20160715-2233 > Reporter: Ondrej Dockal > Priority: Critical > > In .ftl file when using <# and opening code assistant, there are missing directives: compress, nt and setting. I checked http://freemarker.org/docs/ref_directive_alphaidx.html for supported directives but did not find any reason we are missing those mentioned above. -- 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