Active 1 year, 2 months ago. Viewed times. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Who owns this outage? Building intelligent escalation chains for modern SRE. Podcast Who is building clouds for the independent developer?
It looks like it'll fix it for you. Your IDEs aren't helping you. Forget the tools. Fix your directory structures and package names using a text editor. If they are correct, both IDEs will accept them. Learn the language, not the IDE. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.
Email Required, but never shown. The Overflow Blog. Many of the web browsers have also removed support for running applets. There are various tutorials for JavaFX available on the web — see for example this one at tutorialspoint. If you really need support for applets in BlueJ, your only option is to use an older version of BlueJ 3.
The latest versions of BlueJ 4. For other languages, you will have to make your own translation. All labels, menus and dialogues have to be translated.
We are looking for volunteers to do that. Here is how. In the lib directory, you will find subdirectories named "english", "german" and "swedish" and so on. These contain all the language dependent texts. Create a new directory for the language you want. Let's say you want to make a language setting for Elvish. In that case, make a directory named "elvish". Then copy all the files out of one of the other language directories into your new language directory.
They are all text files. Edit each of those files and translate all the texts in them to Elvish keeping the format of the files as it is , then run the "native2ascii" utility that comes with the JDK to convert the files to the correct format.
Once you have done that, you can switch the Elvish language setting on as described above, using the property setting: bluej. Someone out there might just be looking for a translation into your language, too. On Windows you can use the Notepad application to edit the files, but you will need to select "All files" as the file type in the "Open file" dialog.
Furthermore, you may need to save the file to a different location using "save as" and then copy it over the original file using the Windows Explorer if you are unable to save over the original file directly. BlueJ actually runs two Java VMs: One is for BlueJ itself, and the other runs user code for instance if you instantiate a class the resulting object is created in the user VM.
To specify arguments for the user VM, use the bluej. To specify VM arguments for the primary VM, you need to do something different according to the operating system you are using:. Be warned that changing the Java VM arguments is generally unnecessary and if done improperly can prevent BlueJ from functioning correctly. Since BlueJ 3. The encoding is specified in the 'project.
You need to change the "file. You can do this by passing -Dfile. See the FAQ question above for how to do this. You should probably specify the same encoding on both the main and the user VM.
The communication occurs between two processes running on your computer - one is for BlueJ itself, and the other is for a "debug VM" which runs your program. Although this communication doesn't go over the network, some firewall software will block this communication which inhibits BlueJ operation. Firewalls generally take one of two approaches to blocking network traffic.
The second approach is to block traffic on a per-program basis. Some firewalls only block incoming connection attempts while other firewalls may also block outbound connections. For BlueJ to work, communication must be allowed when both the source and destination IP address is Note that BlueJ must be allowed to make outbound connections or "act as a client" as well as receive incoming connections or "act as a server".
If your firewall sets rules on a per-program basis, the program you should apply the rules to will usually be the bluej launcher bluej. There are actually multiple copies of the java. You may also need to change the rules for the "javaw. If you use the standard Windows firewall, you can use the following pages to help you configure the firewall:. If you use 3rd party security software, you will need to consult the documentation for that software.
If you have adjusted or disabled your firewall but BlueJ still does not run, you could try performing a clean boot. If BlueJ runs after a clean boot, you can then determine which service prevents BlueJ from running see the instructions on the "clean boot" page. You may be able to leave the service disabled, or contact the vendor for support. On Linux, the firewall will normally be configured correctly, unless you are using custom firewall rules. You should consult your distribution's documentation to determine how to disable or correctly configure both the firewall and SELinux or, try doing a web search or consulting an appropriate user forum.
Recent Debian systems change the kernel's default network settings in a way which Java doesn't seem to like. Some information on why you are seeing the error might be found in BlueJ's debug log, which you can normally see by typing:. You will need to consult your system documentation or 3rd-party software documentation for information on how to configure your firewall software.
Since Java 7u6, the Java accessibility tools are included with Java as standard -- but they are disabled by default. To enable the Java accessibility tools, follow these instructions. You may need to restart your machine afterwards. Screen reader support was significantly improved in version 3. BlueJ does not have a dark theme as such, but you can change many of the colours that it uses in order to reduce visual brightness. This copy of the file will take preference, and you can edit the colours there.
One important set are the foreground text colours which are specified as -fx-fill in the ". The main background colour, and other background colours for scope highlighting, are specified in the. There is presently no way to change the colours that BlueJ uses for other parts of the interface, such as the package diagram. During the installation process, BlueJ needs to write some files.
The error may indicate that you do not have write permission to that directory. If this is the case, you can start java and tell it to use a different directory for temporary files:. This is not a BlueJ-specific issue, but a problem with Windows Installer mechanism, which maybe fixed by one of the following ways:.
Various strange problems may occur when installing BlueJ on Windows; mostly, these problems are due to issues with the Windows installer framework rather than with BlueJ. Some examples:. Using the CCleaner tool has been reported to solve some issues this tool is published by a third party and the BlueJ team can not take responsibility for any problems its use may cause nor provide support for this tool.
To diagnose these problems, you should install BlueJ with Windows Installer logging enabled:. You can now try to read the log file yourself, or send it to the support team. To do the latter, use the support request form , and then send the log as an email attachment when you receive a response from a team member.
Do not attempt to attach a Windows Installer log when initially submitting the form, as it is only designed to accept BlueJ debug logs. Recent versions of BlueJ 4. These versions require Mac OS X Versions 3. On Mac OS X What this means is: you will not be able to run BlueJ 3.
You can however run BlueJ 2. You must make sure that the correct Java version is active in order to run BlueJ. This may happen if the "update API" dialog is shown when an old scenario is opened but may also occur for other dialogs, particularly if you switch to another application while the dialog is shown. This is actually a Java crash, described in bug entries here and here.
BlueJ is itself a Java application, and creates another instance of a Java Virtual Machine in which the user code written in BlueJ is executed. Make sure that the following applications are also granted authorisation in the MDM: Bluej.
Bluej , com. JavaWebStart and com. As the full message text states, this problem is normally caused by firewall software interfering with BlueJ's operation. More information on how to deal with this issue is available here ; see also this linux-specific information. Another possible cause of this problem when running on Windows is that characters in the path to your project including the project name are not representable in the system character set.
This often occurs when you use accented characters or non-English characters in your project path, and is actually due to a Java bug.
If you cannot resolve the problem, you will need to contact the BlueJ support team. If your program requests input, then you must supply the input before the program can continue running! What is happening is that your program is waiting indefinitely for the input that it has asked for.
Generally, you can open the terminal from the 'view' menu and then type into it. Press 'enter' after supplying the input the terminal input is line buffered. As a better solution, you should have your program output a prompt eg. That will cause the terminal window to open automatically. Since you are using Git over the network, it is affected by firewalls.
0コメント