There are two kinds of packages: planned and published. This article is focused on planned packages, which have not yet been published. For more information on packages that have already been published, see also the list of published packages. -- GilbertHerschberger (31 August 2000).
JOS Root Package Hierarchy (See also FullPackageIndex ) | |---java | |---javax | |---jos | |---jos.app | |---%jos.core | |---jos.experimental | |---jos.hal | |---jos.driver | |---jos.security | |---jos.ui | |---jos.util | |---jos.vm | ---jos.net |
org.jos |---org.jos.app |---org.jos.core |---org.jos.experimental |---org.jos.games |---org.jos.io |---org.jos.lib |---org.jos.net |---org.jos.registry |---org.jos.server |---org.jos.util ---org.jos.www
Note that this page from now on only covers JOS root packages (= direct subpackages of jos and org.jos). All other subpackages are found on the pages of the respective root package or in the FullPackageIndex page . This is done to enhance the usability of this page - MarkusPeter
Add new, proposed root packages (= direct subpackages of jos or org.jos ) in this list.
Most of this page was written when JOS was first starting, and the growth of JOS has been much slower than anticipated. JOS should accept any packages it can get, so to speak.
Hierarchical order can still be maintained in two ways. 1) The packages which are formally part of JOS can still have strictly specified names. 2) Jar files can be put into an organized directory structure (such as FHS or other). Informal packages should be left to sprout as needed.
I will check this page periodically for discussion or links to discussion and if no objections appear, in a few months I will delete this proposal and add a statement that other packages will be accepted in CVS and SourceServer.
Every legitimate request for a new package should be honored by the JOS Project. The request for a package should follow these steps:
- make up your own package name from your own initials and product name
- write the interfaces and classes
- test the product
- make it available to everyone
- after everyone has a chance to look at it, discuss how the package might fit into
To do otherwise, we might as well be OrganizedForNothing. - GilbertHerschberger (2 June 1999)