I'm using FDT 3 enterprise with Flex 4.5 SDK on Mac OSX
Running works fine.
Debugging throws an internal error:
java.lang.NullPointerException
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.versionParts(FDBVersionTools.java:44)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.compare(FDBVersionTools.java:19)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.lessOrEqual(FDBVersionTools.java:7)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.inRange(FDBVersionTools.java:54)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexSdkVersionTools.covers(FlexSdkVersionTools.java:25)
at com.powerflasher.fdt.internal.core.debugger.adapter.FDBAdapterLoader.cover(FDBAdapterLoader.java:51)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexDebuggerLoader.searchAdapterLoader(FlexDebuggerLoader.java:88)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexDebuggerLoader.loadDebugger(FlexDebuggerLoader.java:81)
at com.powerflasher.fdt.core.launch.DebugSessionManager.getDebuggerFor(DebugSessionManager.java:50)
at com.powerflasher.fdt.core.launch.DebugSessionManager.launchSessionFor(DebugSessionManager.java:106)
at com.powerflasher.fdt.core.launch.DebugSessionManager.launchSessionAndKillOld(DebugSessionManager.java:146)
at com.powerflasher.fdt.ui.launch.StartDebuggerTestLaunchConfigurationDelegate.startDebugger(StartDebuggerTestLaunchConfigurationDelegate.java:36)
at com.powerflasher.fdt.internal.ui.launch.fcsh.MxmlcLaunchConfigurationDelegate.startDebugger(MxmlcLaunchConfigurationDelegate.java:348)
at com.powerflasher.fdt.internal.ui.launch.fcsh.AbstractFCSHLaunchConfigurationDelegate.launch(AbstractFCSHLaunchConfigurationDelegate.java:174)
at com.powerflasher.fdt.internal.ui.launch.fcsh.MxmlcLaunchConfigurationDelegate.launch(MxmlcLaunchConfigurationDelegate.java:237)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
I'm not using any uncommon debug/compiler-arguments
Has anyone seen this before?
The Flex Debugger API changed quite a bit from Flex 3.X - 4.0. This means that your older FDT (version 3.x) is likely not compatible with later Flex SDKs. That is why you are getting that error.
You'll need to upgrade to 5.5 (or FDT 4.5 if you have a FDT 4 license)b/c the FDT team has had to rewrite parts of the debugger to make it compatible with Flex 4.5+. We've done our best to keep the upgrade price minimal.
http://fdt.powerflasher.com/buy-download/
Related
I am upgrading openwebbeans project from openJDK12 to OpenJDK17 . currently webeans version is being used 2.0.10 . When upgrading application is not coming up. Is there any apachewebbeans version supporting java 17 and in near future any plan?
UPDATE: OWB-2.0.27 is compatible to JDK17 without having to change the xbean- libraries.
According to this site (https://openwebbeans.apache.org/download.html) OWB-2.0.x should support Java17.
It uses a shaded version of ASM-9 (Java17 support) for building our proxies and requires JavaSE 8 as minimum version.
But i have also problems getting the OWB-2.0.26 version to run with JDK17 because of the used xbean-asm9-shaded lib which only supports java up to version 16.
I have installed eclipse on my iMac and when I try to open it, it gives me this error:
Failed to find a Main Class in
"/Applications/Eclipse.app/Contents/MacOS//../Eclipse/ plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar".
On my MacBook Pro, everything works fine, but I have done nothing different.
I have checked other posts, but most of them refer to a windows OS. There was an answer which said that it can just open when everything is in an English folder and this is true for me!
Thanking you in advance!
I came across this error after installing Eclipse PDT.
Open your terminal and run the version command: java -version.
If your java version is below 1.8, you will have to update your Java
Runtime Environment to at least 1.8.0 by installing an updated JDK
here.
Then re-run the java version command and your version
should be updated.
You should now be able to install and run
Eclipse.
I have the same issue, but on my MacBookPro. I first installed eclipse Photon, which when starting up prompted me to install Java 6, which I did from https://support.apple.com/kb/DL1572?locale=en_US
Then I also installed the latest JRE (jre-8u171-macosx-x64 as of yesterday). When running eclipse again I started getting this error. Then I tried to run from the command line, and got this error:
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/eclipse/equinox/launcher/Main : Unsupported major.minor version 51.0
When googling that, the answers said that the reason for that is that the Oracle installer does not update the symlink in /usr/bin, which seemed to be confirmed by the fact that running java -version returned this:
java -version
java version "1.6.0_65"
The solutions I found for that were not feasible in MacOS starting in version El Capitan, and I am on High Sierra, so I followed the instructions in this post to fix that, and it worked, now I get:
java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)
After all of this, however, I get the same "Failed to find a Main Class" error on the dialog as reported initially here, and the same "UnsupportedClassVersionError" on the CLI that I had when the system was still on java 6, so now I am still stuck and out of ideas.
EDIT: FIXED IT!!
I kept thinking that the problem was the java version, it was somehow still using java 6 (which I had installed due to the initial prompt).
So I followed the instructions here to remove what I had installed for the alleged java 6 issue. Then I found this post in the eclipse forums, which stated at the end (comment added by Eric Rizzo on Tue, 14 February 2017 21:56) that this is not an Eclipse message, but rather an OS message, and that one should NOT do that as apple messed things up with that patch. And then it goes to explain that one should install java 8 JDK (NOT just the JRE as I had done). Once I removed Java 6 and installed the full java 8 JDK, it ran fine :)
You can edit the eclipse.ini with your vm configuration in the beginning of the file
-vm
/yourJvmPath/jdk-12.0.1.jdk/bin/java
cat /Applications/Eclipse.app/Contents/Eclipse/eclipse.ini
-vm
/Users/SomeUser/jdk-12.0.1.jdk/bin/java
-startup
../Eclipse/plugins/org.eclipse.equinox.launcher_1.5.400.v20190515-0925.jar
--launcher.library
../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.1000.v20190125-2016
PD. It works with ApacheDirectoryStudio for MAC
This one works for me with MAC OS Mojave.
You can download the Java SE Development Kit 8u221 for mac from the below link.
jdk-8u221-macosx-x64.dmg
https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I am trying everything I can for the last 3 days and I didnt find a way to make this version of their SDK work with the latest unity version (4.3.1).
FB SDK version 4.2.4 works fine on every Unity version I tried, but, 4.3.6 doesnt work with any of them (4.0, 4.1, 4.2 and 4.3).
Always gives me that weird message about java building:
Error building Player: Win32Exception: ApplicationName='C:Program
Files (x86)Javajre7binjavac.exe', CommandLine='-bootclasspath
"E:/adt-bundle-windows/sdk/platforms/android-14android.jar" -d
"E:Unity Projects[project name]TempStagingAreabinclasses" -source 1.6
-target 1.6 -encoding ascii "comfacebookandroidR.java" "comwinterbigbangR.java"', CurrentDirectory='E:Unity Projects[project
name]TempStagingAreagen
Another weird thing, I setup my app to android 2.3.3 (API-10) why the hell it is trying to use android14?
With the combination of Unity 4.3.1 and FB SDK 4.2.4, I finally made it work flawless, but, I think that Ill be missing some good stuff from 4.3.6...
After almost a week long I think I found the problem.
I uninstalled all Java from my computer and installed Java 6 32bits. Now everything works as intended.
I'm running Eclipse with RoboVM plugin and I wanted to try IOSDemo sample project described on robovm.org (http://www.robovm.org/docs.html). When creating the project in Eclipse and running it I got following error message.
An internal error occurred during: "Launching IOSDemo".
java.lang.IllegalAccessError: tried to access method java.lang.Object.clone()Ljava/lang/Object; from class soot.toolkits.scalar.LocalSplitter
I found out that it's related to JDK version (I'm running JDK 8.0 ea, build 112). When running on JDK 1.7.0_45 and building the project on cmd line it builds and runs OK.
Is it known problem, is there any workaround or fix? Thanks
This is most probably due to a bug [1] in the recent early access builds of Java8. It looks like the bug was resolved a few days ago but as far as I can see the fix didn't make it into the b113 build. Please use the latest Java7 release or an earlier Java8 EA build until a Java8 build is available with this fix included.
[1] https://bugs.openjdk.java.net/browse/JDK-8026394
I recently added a static library (mobclix) to my iPhone project which required me to set the Base SDK to 3.0. This library is claimed to be compatible with 2.2 and so far it looks like it's true. I set the project's Deployment Target to 2.2. No problems there.
Now, I am also using libxml2 in this same project. Apparently, the libxml2.2.dylib in OS 3.0 is newer than in OS 2.X (version 10 and 9 respectively). However, my code that uses libxml2, was already compatible with the libxml2 version included with OS 2.X. Since I needed to set the Base SDK to 3.0, the "compatibility version" / minimum version requirement / dependency is automatically set to the newer version of libxml2. When I try to run the app in OS 2, I get this runtime error (obviously):
Dyld Error Message:
Library not loaded: /usr/lib/libxml2.2.dylib
Referenced from: /Users/Martijn/Library/Application Support/iPhone Simulator/User/Applications/4D5456DE-F297-4DF4-ACA6-DA8BBBBBA914/Luisterpaal.app/Luisterpaal
Reason: Incompatible library version: Luisterpaal requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
Is it possible to override the version requirement somewhere?
Or other ideas to solve this issue?
The compatibility version is set according to the version embedded in the dylib of the current SDK during build. I have not found a way to change or override this.
However, in the target in Xcode under the "Link with binary with libraries" branch there is an option to link a dylib "weakly". This skips version checking at the time of loading the dylib (runtime). It's your responsibility then to only make calls to existing functions. Making calls to non-existent functions will crash the application.
Apparently there was a change with SDK 3.0 that broke compatibility with libxml. Apple have posted about it here:
http://developer.apple.com/iphone/library/qa/qa2009/qa1659.html