-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the Test.app supposed to do something other than fail? #44
Comments
Adam, I can't really speak for the problem with Test.app, other than having experienced it myself. The only possibly useful thing I might ask about, though, is that it is trying to start from What I would like to comment is the list of args in your output above. Note that the set of 34 args is repeated. This means that the second set are all passed to the I ran into this yesterday because an app of mine using the latest and greatest appbundler was checking for command-line args, and it complained up a storm about the 30+ unknown options it was being given. Spent an hour or two trying to figure out what was causing this, but other than determining it arose in one of the last commits made to appbundler before @sreilly officially moved it from Bitbucket to Github, I didn't get anywhere. |
@msdsoftware What you ran into yesterday sounds a lot like my report in #45. |
The tasks for building Test.app and TestPlugin.app both place SwingInterop.jar in the classpath, but where is it? Some time with the Google suggests this is something dating back to JavaFX in 2012, and frankly is no longer compatible with appbundler. |
If we could get Test.app into a working state, we could use it to create a continuous integration test so that all PRs and commits could be confirmed not to break the test scenarios. We could set it up so that multiple JDKs are tested. |
After mucking about for too long, and scrounging up a copy of SwingInterop.jar off the net, I finagled a way to get Test.app to launch and show me something. What I got was a dialog requiring that I download a newer Java. Same result with several different JDKs. However, launching SwingInterop.jar does work if I simply doubleclick on the jar icon. |
Actually, SwingInterop.jar does not launch when I doubleclick — instead a security popup appears. It does launch if I control-click on it and indicate I want to open it using Jar Launcher. I get the download msg because Jar Launcher is either using the JRE 10 or JDK 9 installed on the machine. Decompiling, I see that SwingInterop.jar is hard-coded to require Java 1.7, 1.8 or 1.9. (Yes, "1.9", not "9".) So creating Test.app looks useless unless your system has no Java newer than 8 installed. |
Running
ant test
leaves aTest.app
in the project folder. Double-clicking on this app results in a dock icon briefly appearing, then disappearing. Running the application from the command line yields errors:Does anyone know what the expected behavior is for Test.app?
The text was updated successfully, but these errors were encountered: