File name conventions used within Naked Objects distributions

File names

The names given to the download files indicate what the product is, which platform it runs on and its version. The version indicates the stage of development and how stable the system should be. The file name format is as follows:

nakedobjects-[version]-[type].[file-type]

For example:-

nakedobjects-4.0.1-for-maven.zip
nakedobjects-4.0-for-ant.tar.gz
nakedobjects-4.0-libs-only-with-dependencies.jar 
nakedobjects-4.1-source.zip

The parts of the name are:

version
See next section
type
We provide the framework in a number of ways depending on how you want to work with it. The source is the most basic and requires the most work before the framwork can be used. This distribution allows you to regenerate the distributions, but does require Maven. The source distribution is simply an alternative to checking the code out from the Subversion repository. The for-maven and for-ant distributions provide all the required files to develop and run applications using the Maven and Ant build tools. The maven distribution is relatively small download as framework libraries are downloaded by Maven only when you actually build an application. An alternative to complete package is the libs-only-with-dependencies, which simply provides all the classes for the framework and dependent libraries in a single jar file that can be added straight to the class path, so there is no need to unpack it.
file-type
The file type is jar, zip or tar.gz (GNU compressed tar).

Versions

n.n.n
Stable release, with version number split into major, minor and fix components. Major versions develop upon, but do not limit themselves to, the previous major version. Minor versions extend the previous version while maintaining compatibility with them. Fix versions fix problems in the existing version, but do not add any new functionality.
n.n-alpha-n or n.n-beta-n
Development release are releases are relatively stable versions of the framework that introduce new functionality that is part of the development plan for the versioned release. The milestones precede the versioned releases, that is 4.1-alpha-1 will be released as part of the development of 4.1. Functionality within the alpha or beta release for a major version is not fixed and may change as further development takes place.
n.n-wip-n
Work in progress releases are made during the development of the current version to exhibit a particular state of develop - such as new features, major changes or important bug fixes. These should generally be stable as they are not normally released when the code has known major problems.
n.n.n-SNAPSHOT
Snapshot releases are available from every completed build, and hence may not even be runnable, depending the state of development. These are generally a way to keep up with latest development without using subversion.