[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-20915:
----------------------------------------
[~xcoulon], [~mhusnain] I think http://tools.jboss.org/documentation/faq/ is the best place for that. I'm moving it to CR1 but feel free to resolve it for Beta2 if you have time.
> HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20915
> URL: https://issues.jboss.org/browse/JBIDE-20915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20150925-1252-B116
> Reporter: Vlado Pakan
> Assignee: Misha Ali
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Make some changes to opened page and save them.
> ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser.
> Repeat step 4. couple of times
> ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20915:
-----------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20915
> URL: https://issues.jboss.org/browse/JBIDE-20915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20150925-1252-B116
> Reporter: Vlado Pakan
> Assignee: Misha Ali
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Make some changes to opened page and save them.
> ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser.
> Repeat step 4. couple of times
> ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20915:
--------------------------------------
Assignee: Xavier Coulon (was: Misha Ali)
> HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20915
> URL: https://issues.jboss.org/browse/JBIDE-20915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20150925-1252-B116
> Reporter: Vlado Pakan
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Make some changes to opened page and save them.
> ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser.
> Repeat step 4. couple of times
> ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20915:
-----------------------------------
Priority: Major (was: Critical)
> HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20915
> URL: https://issues.jboss.org/browse/JBIDE-20915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20150925-1252-B116
> Reporter: Vlado Pakan
> Assignee: Misha Ali
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Make some changes to opened page and save them.
> ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser.
> Repeat step 4. couple of times
> ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20797) CCE on first start on clean install of CR1
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20797?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-20797.
------------------------------------
Resolution: Done
We are updating the TP for Beta2. Should be fixed there. Resolving.
> CCE on first start on clean install of CR1
> ------------------------------------------
>
> Key: JBIDE-20797
> URL: https://issues.jboss.org/browse/JBIDE-20797
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> clean install of eclipse JEE + CR1 jbosstools for mars.
> Get this error on startup on a clean workspace:
> {code}
> java.lang.ClassCastException: [Lorg.eclipse.swt.graphics.FontData; cannot be cast to java.lang.String
> at org.eclipse.ui.internal.themes.Theme$1.propertyChange(Theme.java:124)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:351)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:347)
> at org.eclipse.jface.preference.PreferenceConverter.setValue(PreferenceConverter.java:463)
> at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.ensurePreferenceStoreBackwardsCompatibility(JavaScriptPlugin.java:395)
> at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.start(JavaScriptPlugin.java:336)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
> at org.eclipse.osgi.container.Module.doStart(Module.java:571)
> at org.eclipse.osgi.container.Module.start(Module.java:439)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
> at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.editorOpened(JavaEditorTracker.java:157)
> at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.partOpened(JavaEditorTracker.java:152)
> at org.eclipse.ui.internal.WorkbenchPage$18.run(WorkbenchPage.java:4939)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartOpened(WorkbenchPage.java:4936)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$2.handleEvent(CompatibilityPart.java:121)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.basic.impl.PartImpl.setObject(PartImpl.java:410)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:131)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:99)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:494)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:458)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:724)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:396)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1166)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3234)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3149)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3131)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3126)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3090)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3071)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:436)
> at org.jboss.tools.central.JBossCentralActivator$6$1.run(JBossCentralActivator.java:411)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21290:
-------------------------------------
This is awaiting upstream API. However, the solutions being suggested upstream don't seem to be addressing finding a version for the CDK but rather its underlying pieces. More discussion will be needed.
> CDK 2 is detected as version 1.0
> --------------------------------
>
> Key: JBIDE-21290
> URL: https://issues.jboss.org/browse/JBIDE-21290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, runtime-detection, upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png
>
>
> When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0.
> !cdk-runtime-detection.png!
> Could we change it to version 2?
> I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21293) CDK start timed out due to slow image download
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21293?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21293:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> CDK start timed out due to slow image download
> ----------------------------------------------
>
> Key: JBIDE-21293
> URL: https://issues.jboss.org/browse/JBIDE-21293
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> I set up a CDK server using https://github.com/redhat-developer-tooling/openshift-vagrant .
> Then I tried to start the server for the first time. Of course this will take quite long as it needs to download the VM image first. I was on a very fast connection, but it still only went around 1 MB/s. So the startup took longer than the default timeout of 450 s. The result was that the startup timed out in the middle followed by an attempted shutdown by the tooling which failed. So in the end I ended up with the running box, but with two unwanted errors.
> I'm not sure what we can do here. Perhaps just increase the timeout to something bigger? Even better would be if could detect that a download is in progress so it will take longer, but I don't think the current mechanism is capable of anything like that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21315) CDK: Missing PATH for vagrant and VBoxManage on Mac
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21315?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21315:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> CDK: Missing PATH for vagrant and VBoxManage on Mac
> ---------------------------------------------------
>
> Key: JBIDE-21315
> URL: https://issues.jboss.org/browse/JBIDE-21315
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> It seems there is no JIRA to track this specifically yet.
> The problem is that CDK tooling relies on PATH to find vagrant. And the "vagrant up" command in turn depends on PATH to find e.g. VBoxManage.
> On Mac, when you start your Eclipse / JBDS as an app by double-clicking an icon on your Desktop or in Finder, the Eclipse instance will have no PATH env variable.
> One workaround is to start your Eclipse from command line by going inside the package:
> {code}
> cd Eclipse.app/Contents/MacOS
> ./eclipse
> {code}
> But this is definitely not the recommended way to start Eclipse - I'm not sure if eclipse.ini is located properly in this case. But at least PATH is correct then.
> There is actually one more workaround. To add your PATH to the Environment tab in Launch config. That works for me.
> So that might be a potential solution to this problem - have a predefined PATH for each OS in case there is none defined in the Eclipse process.
> Previous related JIRAs:
> JBIDE-21175 [CDK] Require better logic to find vagrant.exe / vagrant command
> JBIDE-21172 CDK server in Starting state and cannot be stopped with wrong path to vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-471) Unify component versions
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ]
Robert (Bob) Brodt commented on JBTIS-471:
------------------------------------------
I think I've got them all. Can we call this one done?
> Unify component versions
> ------------------------
>
> Key: JBTIS-471
> URL: https://issues.jboss.org/browse/JBTIS-471
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 8.0.3.GA
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Attachments: junit4.8vs4.12.png
>
>
> Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as
> BPMN2 1.1.3.Final
> Fuse 7.3.1.v20150728-1330-H54-Final
> Teiid Designer 9.0.3.Final-v20150728-2029-B1148
> I suggest to use the format used by Teiid Designer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months