[JBoss JIRA] (JBIDE-22631) FreeMarker Editor regression or configuration question
by Daniel Dekany (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22631?page=com.atlassian.jira.plugi... ]
Daniel Dekany edited comment on JBIDE-22631 at 7/30/16 8:14 AM:
----------------------------------------------------------------
While surely it did something before, I doubt it ever work correctly. Freely(!) mixing fragments of two independent languages means that you have to nest two partitioning logics in each other, or at least you have to able to look back to earlier partitions when repartitioning, and I don't see how the current partitioner could support that. Anyway, properly supporting HTML editing is a project in itself (and ideally it includes JavaScript and CSS support), and it was already done in Eclipse WTP. So I think, just like in the Eclipse PHP plugin, it should be leveraged (they call this thing a structured text editor; see also {{PHPStructuredTextPartitioner}}).
Ps.: There was an attempt on using WTP-s HTML capability long ago... I don't know how far it get though: https://github.com/angelozerr/Freemarker-Eclipse-DLTK
was (Author: ddekany):
While surely it did something before, but I doubt it ever work correctly. Freely(!) mixing fragments of two independent languages means that you have to nest two partitioning logics in each other, or at least you have to able to look back to earlier partitions when repartitioning, and I don't see how the current partitioner could support that. Anyway, properly supporting HTML editing is a project in itself (and ideally it includes JavaScript and CSS support), and it was already done in Eclipse WTP. So I think, just like in the Eclipse PHP plugin, it should be leveraged (they call this thing a structured text editor; see also {{PHPStructuredTextPartitioner}}).
> FreeMarker Editor regression or configuration question
> ------------------------------------------------------
>
> Key: JBIDE-22631
> URL: https://issues.jboss.org/browse/JBIDE-22631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Environment: Windows 7
> Reporter: Paul Verest
> Fix For: 4.5.x
>
> Attachments: freemarker-editor.PNG
>
>
> As initially raised at https://github.com/jbosstools/jbosstools-freemarker/issues/59
> latest FreeMarker Editor plugin (v of 2016) appear less functional than v of 2009, e.g. only highlight for freemarker syntax, but not any HTML support.
> Both where installed in recent Eclipse Mars.
> Or possibly something should be configured for FreeMarker Editor to support HTML editing as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (JBIDE-22631) FreeMarker Editor regression or configuration question
by Daniel Dekany (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22631?page=com.atlassian.jira.plugi... ]
Daniel Dekany commented on JBIDE-22631:
---------------------------------------
While surely it did something before, but I doubt it ever work correctly. Freely(!) mixing fragments of two independent languages means that you have to nest two partitioning logics in each other, or at least you have to able to look back to earlier partitions when repartitioning, and I don't see how the current partitioner could support that. Anyway, properly supporting HTML editing is a project in itself (and ideally it includes JavaScript and CSS support), and it was already done in Eclipse WTP. So I think, just like in the Eclipse PHP plugin, it should be leveraged (they call this thing a structured text editor; see also {{PHPStructuredTextPartitioner}}).
> FreeMarker Editor regression or configuration question
> ------------------------------------------------------
>
> Key: JBIDE-22631
> URL: https://issues.jboss.org/browse/JBIDE-22631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Environment: Windows 7
> Reporter: Paul Verest
> Fix For: 4.5.x
>
> Attachments: freemarker-editor.PNG
>
>
> As initially raised at https://github.com/jbosstools/jbosstools-freemarker/issues/59
> latest FreeMarker Editor plugin (v of 2016) appear less functional than v of 2009, e.g. only highlight for freemarker syntax, but not any HTML support.
> Both where installed in recent Eclipse Mars.
> Or possibly something should be configured for FreeMarker Editor to support HTML editing as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBTIS-654:
-------------------------------------
Just open new JIRA for progress bar after you done with this one.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (JBIDE-22759) Error logged from Debug UI when EAP is started
by Daniel Dekany (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22759?page=com.atlassian.jira.plugi... ]
Daniel Dekany edited comment on JBIDE-22759 at 7/30/16 3:28 AM:
----------------------------------------------------------------
This problem should be gone with the recent JBIDE-22701 update, from about a week ago. It was merged but Fix version is set to "4.4.1.AM3".
was (Author: ddekany):
This problem should be gone with the recent JBIDE-22701 update.
> 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)
7 years, 9 months
[JBoss JIRA] (JBIDE-22759) Error logged from Debug UI when EAP is started
by Daniel Dekany (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22759?page=com.atlassian.jira.plugi... ]
Daniel Dekany commented on JBIDE-22759:
---------------------------------------
This problem should be gone with the recent JBIDE-22701 update.
> 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)
7 years, 9 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3951:
--------------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3951:
-----------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months