[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon commented on ERT-204:
-----------------------------------
[~mmalina]: yes, the fix version is "Linux Tools 5.1.0" (which is the umbrella project/version for Docker tooling 2.1.0). The target release will be Neon.1 but we might have it in JBoss Tools target platform earlier, when it is updated.
> Docker Machine lookup does not work on Windows machines [EBZ#494305]
> --------------------------------------------------------------------
>
> Key: ERT-204
> URL: https://issues.jboss.org/browse/ERT-204
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[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:
---------------------------------------
For some reason there is still no new build of master/AM3, so I cannot verify this yet.
> 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
[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22810:
---------------------------------------
I've tried, several times but I am not able to reproduce it. I am using devstudio 10.0.1.AM2 build ID AM2-v20160725-1821-B5680.
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Viacheslav Kabanovich
> Fix For: 4.4.1.AM3
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22654) If image name ends with spaces, deploy is not possible
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22654?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22654.
---------------------------------
Verified in devstudio 10.0.1.AM2 build ID AM2-v20160725-1821-B5680.
> If image name ends with spaces, deploy is not possible
> ------------------------------------------------------
>
> Key: JBIDE-22654
> URL: https://issues.jboss.org/browse/JBIDE-22654
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: openshift, openshift_v3
> Fix For: 4.4.1.AM2
>
> Attachments: screenshot-1.png
>
>
> From the Docker explorer, select an image and click Deploy to Openshift. If the image name is right padded with spaces, the next button is grayed. [^screenshot-1.png]
> We shoud trim the image name
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22860:
-------------------------------------
Summary: Application Wizard: Improve layout for templates
Key: JBIDE-22860
URL: https://issues.jboss.org/browse/JBIDE-22860
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.1.AM2
Reporter: Marián Labuda
Priority: Minor
In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22860:
----------------------------------
Labels: application_wizard openshift_v3 (was: )
> Application Wizard: Improve layout for templates
> ------------------------------------------------
>
> Key: JBIDE-22860
> URL: https://issues.jboss.org/browse/JBIDE-22860
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3
>
> In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22592) Application wizard: Failed even though provided required value to parameters
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22592?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22592.
---------------------------------
Verified in devstudio 10.0.1.AM2 build ID AM2-v20160725-1821-B5680.
> Application wizard: Failed even though provided required value to parameters
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22592
> URL: https://issues.jboss.org/browse/JBIDE-22592
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBoss OpenShift 3 Tools 3.3.0.Final-v20160610-1836-B1369
> JBoss OpenShift 3 Tools Developer Resources 3.3.0.Final-v20160610-1836-B1369
> Eclipse: Neon Milestone 7 (4.6.0M7)
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.1.AM2
>
> Attachments: application-template-stibuild.json, fails-even-though-required-value-provided.png, Screenshot from 2016-06-12 01-59-02.png
>
>
> Create app from the local template in attachment,give required value to parameter "xiazhao_checkfail" inside new-app wizard, get error message after clicking on the "Next>" button:
> Template "ruby-helloworld-sample" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified
> Could not create resource ruby-helloworld-sample in namespace 'xiazhao-1': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Template \"ruby-helloworld-sample\" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","reason":"Invalid","details":{"name":"ruby-helloworld-sample","kind":"Template","causes":[{"reason":"FieldValueRequired","message":"Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","field":"template.parameters[5]"}]},"code":422}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months