We’ve installed the new Flex 3 Beta with ant support and checked iFac in this enviroment!
Everything has worked perfect and so you’re also be able to compile mxml with iFac!
(see also: samples page)
We’ve installed the new Flex 3 Beta with ant support and checked iFac in this enviroment!
Everything has worked perfect and so you’re also be able to compile mxml with iFac!
(see also: samples page)
Great work, thanks very much. Im attempting to use iFac with Eclipse 3.3 and Flex 2 SDK and the latest JRE 1.6.0_03, but when I attempt to run the Ant task the JRE accvio’s. Have you experienced this and if so what is the appropriate workaround, downgrade the JRE, or other?
[ifac] #
[ifac] # An unexpected error has been detected by Java Runtime Environment:
[ifac] #
[ifac] # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c362665, pid=13328, tid=13920
[ifac] #
[ifac] # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode)
[ifac] # Problematic frame:
[ifac] # C [MSVCR71.dll+0x2665]
[ifac] #
[ifac] # An error report file with more information is saved as hs_err_pid13328.log
[ifac] #
[ifac] # If you would like to submit a bug report, please visit:
[ifac] # http://java.sun.com/webapps/bugreport/crash.jsp
[ifac] #
I just tried with JRE 1.5.0_06 and got a similar error, with a slightly different address of course:
[ifac] # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x77c47e9f, pid=812, tid=5420
[ifac] #
[ifac] # Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode)
[ifac] # Problematic frame:
[ifac] # C [MSVCRT.dll+0x37e9f]
Suggestions?
I don’t know if this has any applicability or not, but I found the following comment in the Java SE 6 release notes for Windows.
Java SE 6 applications that use custom launchers must be installed with msvcr71.dll in the same directory as the launcher executable. This follows the new Windows C runtime distribution model, per http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_CRT_C_Run.2d.Time_Libraries.asp.
Please feel free to move or remove my comments if they are appropriate for general consumption or if they should be posted elsewhere.
hi. thanks for this nice little plugin. its working perfectly on my system [win xp 32 with europa & fdt3]. however when i build through ifac i get in the console a lot of “[ifac] protocol error” messages. these dont seem to be indicating anything is wrong though since my source compiles correctly with fcsh [and quickly too!]
any hint as to why are these errors coming up?
Hi there,
i know this issue and fixed it in the upcoming release. The “protocol error” messages don’t indicate an error as they we’re mentioned to do – in windows they are always shown if a blank line is sent from fcsh.
We’ll publish the next version in the next days.
Regards,
Florian Diesner
cool.. on another topic is there any possibility of linking compile errors in the console to the culprit class and line? this would be a huge convenience! keep up the go
*keep up the good work!
Thanks dontsave,
linking the errors is currently on our TODO-List and will be implemented soon.
Regards,
Florian Diesner
Hi, after I installed the plugin, I cannot start any eclipse related application when the following logs… any idea?
!ENTRY org.eclipse.osgi 4 0 2008-07-03 16:16:18.707
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: Cannot initialize Drop
at org.eclipse.swt.dnd.DND.error(Unknown Source)
at org.eclipse.swt.dnd.DND.error(Unknown Source)
at org.eclipse.swt.dnd.DropTarget.(Unknown Source)
at org.eclipse.ui.internal.EditorSashContainer.addDropSupport(Unknown Source)
at org.eclipse.ui.internal.EditorSashContainer.createControl(Unknown Source)
at org.eclipse.ui.internal.EditorAreaHelper.(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.init(Unknown Source)
at org.eclipse.ui.internal.WorkbenchPage.(Unknown Source)
at org.eclipse.ui.internal.WorkbenchWindow.restoreState(Unknown Source)
at org.eclipse.ui.internal.Workbench.doRestoreState(Unknown Source)
at org.eclipse.ui.internal.Workbench.access$14(Unknown Source)
at org.eclipse.ui.internal.Workbench$19.run(Unknown Source)
at org.eclipse.ui.internal.Workbench.runStartupWithProgress(Unknown Source)
at org.eclipse.ui.internal.Workbench.restoreState(Unknown Source)
at org.eclipse.ui.internal.Workbench.access$12(Unknown Source)
at org.eclipse.ui.internal.Workbench$17.run(Unknown Source)
at org.eclipse.core.runtime.SafeRunner.run(Unknown Source)
at org.eclipse.ui.internal.Workbench.restoreState(Unknown Source)
at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(Unknown Source)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(Unknown Source)
at org.eclipse.ui.internal.Workbench.init(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
at org.eclipse.core.launcher.Main.run(Unknown Source)
at org.eclipse.core.launcher.Main.main(Unknown Source)
You may possibly have not intended to try and do so, but I consider you’ve managed to express the state of thoughts that a whole lot of men and women are in. The sense of looking to help, but not knowing how or where by, is something a whole lot of us are planning through.