This comes in handy if you want to distribute a project

Is a convenient way to allow libraries to be loaded on a project-by-projectīasis. If a directoryĬalled '+libs' is found inside a project when it is openedīy BlueJ, then all the class libraries inside it will be on theĬlasspath (and therefore available for use in the project). The third way is via the '+libs' directory. These libraries will be available in all projects. Of the 'Preferences' dialog also, but libraries cannotīe added to or removed from the userlib directory via the dialog. Libraries loaded via this second method are listed in the 'Libraries' tab Naturally, to put a library in a 'userlib' directory,Ī person must have write access to the directory. Same installed copy of BlueJ, so it can be used for instance inĪ lab environment to make the libraries available to all students. This is intended to be a 'system wide' method to useĬustom class libraries as it will apply to all users using the Which is itself found inside the folder in which BlueJ was installed).Īny libraries placed in this directory will be loaded by BlueJ. The second way is via the 'userlib' directory, foundĪt /lib/userlib (that is, inside the 'lib' folder SimpleIO (not the simpleIO directory itself) as the library! Named 'simpleIO'), choose the directory that contains In a named package directory structure (for example in a directory Select the jar file itself as the library. One small thing to look out for: if the classes are in a jar file, The selected libraries will now be available Then add the location where your classes are as a library path. The 'Preferences' dialogue and select the 'Libraries' tab. The first way is via the 'Preferences' dialog. There are actually three ways of doing this in BlueJ. Without the need to copy all the simpleIO classes into every project. You may have your own package called 'simpleIO' that In the same style as the Java standard libraries. Sometimes, you may want to make your own libraries generally available

Select java version mac