compile-while-executing
You cannot compile while the machine
is executing. This could cause strange
problems!

exception-thrown
An exception was thrown:

break-no-source
Breakpoint hit in a file for which the
source cannot be found.  Filename:

error-in-file
An error occurred in a file for which the
source cannot be found.
class: source line number:

system-exit
The method finished through an explicit
"exit" instruction. No result was
returned. The exit code is:

no-help
No help available for this message.
Please mail the text of the error message
to mik@bluej.org - we will then
add a help text to our help database. Thanks.

editor-crashed
It seems that BlueJ crashed while writing this class
to disk last time. The source code may be missing or 
incomplete. There should be a backup of this class 
in the project folder. If this class seems damaged,
   1 - quit BlueJ
   2 - backup your project folder (just in case)
   3 - look into the project folder for a backup of
       this java file. Rename it to the original
       file name (with a '.java' suffix)

cannot-run-compiler
Cannot run compiler. Is the
program in your path?
Name of compiler:

compiler-error
Compiler error:

stream-incomplete
Compiler error. Error stream incomplete.

out-of-bounds
Element specified is not
within array bounds.

cannot-access-element
Unable to access the array
element specified.

appletviewer-error
Error executing applet in appletviewer.

error-no-name
You must specify a valid name.

error-save-file
An error occurred when trying to save
the file. The file was not saved.

cannot-save-keys
An error occurred while trying to save
the key bindings. The bindings were not
saved.

error-no-templates
The specified template directory (the directory where
BlueJ finds the class templates) does not exist. It
is defined with the property "bluej.templatePath" in
<bluej-home>/lib/bluej.defs. Check and fix this property.

skeleton-error
The default skeleton for the class could not be
generated. This may be because of configuration
error in the setup of BlueJ, or because of file
system access problems.

error-open-source
Cannot open the source
of this class.

error-writing-readme
The README file for this project could not be
updated to add the main class information.
There was an error changing this file.

error-writing-jar
The jar file could not be written correctly.
(Check the file system for access rights and
disk space availability.)

error-jar-exists
The file you have selected already exists.
Do you want to overwrite it?
Overwrite
Cancel
null

invalid-class-name
Invalid Class Name.

invalid-package-name
Invalid Package Name.

must-be-identifier
The name is not valid. It
must be a Java identifier.

directory-exists
A file or directory with this
name already exists.

cannot-copy-package
There was a problem copying the
package files. The package was
not written or may be incomplete.

file-does-not-exist
The specified file
does not exist.

cannot-import
Cannot import file. The file must
be a Java source file (it's name
must end in ".java").

docdir-blocked-by-file
The directory for the documentation could
not be created in the project directory
because there is a file with same name.

docdir-not-created
The directory for the documentation could
not be created in the project directory.

no-permission-for-docdir
The directory for the documentation could
not be created in the project directory
because of insufficient rights.

show-or-generate
Do you want to show the documentation
generated previously, or do you want
to regenerate the whole documentation?
Just Show
Regenerate
Cancel

doctool-error
Javadoc reported an error. It could be that there is a
syntax error in one of the files you tried to generate
a documentation for. It could also be that the JDK
documentation URL specified in the preferences is incorrect.
Make sure that all your Java files are compiled and the
documentation URL is accessible or disabled. Then try again.
If this message appears again you should check the log file
with the error messages from Javadoc:

severe-doc-trouble
An exception occured during the call
to the external documentation tool.

no-java-sources-found
No Java source files were
found in this directory.

duplicate-name
A class or package with this name already exists
in this project. You cannot have two
classes or packages with the same name.

error-in-import
An error occured during the attempt to
import the file. Check access rights and
disk space.

no-class-selected-compile
No class selected for compilation.
Select a class by clicking on
it before trying to compile.

no-class-selected
Nothing selected for removal.
Select a class, arrow or package by clicking on
it before trying to remove.

really-remove-class
Removing classes will permanently
delete their source file(s).
Do you want to continue?
Remove
Cancel
null

really-remove-package
Removing this package will permanently
delete the package directory (including ALL
the contents of that directory).
Do you want to continue?
Remove
Cancel
null

remove-package-open
The package you have selected for
deletion has some sub-packages opened
within BlueJ. You must close these
packages before you will be allowed
to delete this package.

package-does-not-exist
Error in opening package.
Package does not exist:

no-bluej-package
Error in opening package.
The file/directory is not
a BlueJ package:

applet-height-width
Applet height and width
must be specified.

cannot-read-help
Cannot read help file:

not-yet-implemented
Not Yet Implemented - sorry.

quit-all
Quit all open projects?
Quit All
Cancel
null

really-reload
Reload discards all changes since the last edit.
Are you sure?
Reload
Cancel
null

changed-on-disk
The source file has changed on disk. Do you want to
reload it from disk? This will discard changes made
here in the editor.
Reload
Cancel
null

really-print
The text is wider than the paper. Long lines
will be cut off. You can avoid this by resizing
the editor window to make it narrower. Do you
want to print anyway?
Print
Cancel
null

open-non-bluej-already-bluej
The directory you have selected is already
a BlueJ project.

open-non-bluej-no-java
No Java source files were
found in this directory.

open-non-bluej-invalid
You have indicated you wish to open this
directory as a BlueJ project, however a file
has been found with a package statement that
is incompatible with the current directory
structure. (For example, if the Java class
Shape has a package line of com.aa, then the
file Shape.java must be in a directory aa
which is itself in a directory com. This com
directory in turn must be in another directory
which is the directory you should point BlueJ
to when attempting to open it).

import-into-current
You currently have a package open in this window.
Do you want to import into the current package
or would you like to create a new project and
import into that?
Current
New Project
Cancel

package-name-invalid
You have changed the package statement
to a package which does not exist in this project.
If you wish to move this class to another
package you must create the destination
package first. The package statement has been
reverted back to its original form.

package-name-clash
You have changed the package statement to 
a package that already has a class or package
of this name. If the class is moved, the
existing class or package would be overwritten,
so the package statement has been reverted
back to its original form.

package-name-changed
You have changed the package statement which
tells Java the package this class is in. Do you
want to move this class to the indicated package
or do you want to leave the class where it is
(the package statement will be reverted back to
its original form)?
Move
Revert
null

ask-index
Enter array element index [...]
Array Inspection
null

classmgr-changes-no-effect
The changes you have made to the class libraries
will not take effect until the next time you
compile or restart the Virtual Machine.

unittest-new-test-method
Specify a name for this test.
Recording will then start.
New Test Method
null

getobject-new-name
Enter the name for the new object on the
object bench.
New Object Name
null

unittest-fixture-present
This unit test class already has a fixture declared
in it. If you proceed, the definition of this
fixture will be replaced.
Do you want to continue?
Replace
Cancel
null

unittest-method-present
This unit test class already has a test method declared
within it of the same name. If you proceed, the
definition of the method will be replaced.
Do you want to continue?
Replace
Cancel
null

no-search-string
No search string is defined.
(Highlight some text or use 'Find' first.)

default-keys
Do you really want to discard all your
key bindings and set the default
bindings?
Set defaults
Cancel
null

error-create-vm
BlueJ was unable to create a virtual machine (VM) to execute projects.
This is a serious problem - you will not be able to create objects 
or execute methods without solving it.
Usually, this problem is caused by specific network settings on your
machine. BlueJ uses TCP/IP and sockets to achieve the creation of the 
VM. The most common cause for this is an overly restrictive firewall that
does not allow connections from your local host. Switch off the firewall
(if you have one) to test this. If this solves it, try to find a firewall 
setting that allows connections from localhost.
Other possible causes are incorrect network settings. Check that TCP/IP
is set up correctly check other networking parameters.
If problems persist, ask for help (see http://www.bluej.org/help/ask-help.html).

project-is-readonly
The project is read-only. You will not be able to create objects
or execute methods.
Either the access rights of the project directory are set as 
'read only' for you, or the whole file system is not writable (is 
it a CD?).
To fully use this project, you must ensure that it is on a writable
file system (usually your hard disk), and that you have write 
permission in the project directory and each file within it.
This can often be accomplished by choosing "save as" from the
Project menu after closing this dialog.

could-not-write-shell-file
Execution failed because the project directory is not writable.
To create objects or execute methods, we must be able to write
to the project directory. Make sure your project is on a writable 
file system (not a CD!) and that you have write permission in
the project directory and all files in it.

jar-output-dir-exists
The output directory for the archive being extracted already
exists. You must remove the existing directory before you can
extract the archive.

jar-extraction-error
An error occurred in extracting the archive contents. The debug
log may contain more information.

file-save-error-before-compile
One or more files could not be saved, so compilation was cancelled.

generic-file-save-error
An error was encountered when trying to save a file.

empty-assertion-text
You have not entered an expected result for this method call.
Without this result, your test is incomplete, and your test class will
not compile. Are you sure you want to continue without entering
a result value? 
Go back
Continue
null

team-update-first
There have been changes made to files in the repository, but the files
have been deleted in your working copy. This is a conflict. Before you can
do a commit, you need to perform an update, which will restore the
repository versions. The following files are affected:

team-resolve-conflicts-delete
There are conflicts with some files, which have been modified in the
repository as well as in your working copy. You need to delete your versions
of the following files and then perform an update in order to resolve the
conflict:

team-resolve-merge-conflicts
During a previous update, there were merge conflicts in some files. You need
to edit the following files and resolve the conflicts before you can perform
a commit:

team-unresolved-conflicts
There are unresolved conflicts with the following files. You will
have to delete the files locally to resolve the conflict:

team-uptodate-failed
Your local copy is out of date. Update from repository
before committing your local changes.

team-cant-find-module
Project not in repository. A project must be shared (put 
in the repository) before you can check it out.

team-empty-message
An unknown error occurred. Check the team settings to make sure your
repository settings are correct.

team-invalid-cvsroot
Invalid CVS root - check your team settings.

team-authentication-problem
The server could not log you in - check your username/password and
repository in team settings.

team-binary-conflict
A conflict was detected when trying to update the following file:
    $
The file was changed locally, but there are also changes in the
repository.
Keep my version
Use repository version
null