The various tide systems are zero-tide, tide-free and unknown. They are
available both at force model level and at gravity field provider level.

files.

considered.

Fixes issue #125

We now consider Java 6.0 to be mandatory. Some Java 6 specificities will
be used soon.

Orphan frames correspond to trees that are not yet connected to the main
frame tree but attached later on. This allows building frame trees from
leaf to root.

This change fixes feature request #98.

Conflicts:
	src/site/xdoc/changes.xml

The filtering occurs a priori, i.e. the filtered out events do not
trigger a search. Only the interesting events are searched for and
contribute to computation time.

This change fixes feature request #104.

This framework mimics the one already existing in numerical propagator.

Conflicts:
	src/main/java/org/orekit/propagation/analytical/Ephemeris.java
    Small conflicts in imports, exceptions, and array vs. List syntax.

The ImmutableTimeStampedCache will allow fast access to data that is stored in
memory and not modified. It is now used in AbstractEOPHistory, Ephemeris, and
UTCScale. As a side effect the implementation of EOP loaders is now decoupled
from EOPHistory.

The previous implementation of TimeStampedCache has been renamed to
GenericTimeStampedCache, and the TimeStampedCache interface extracted from it.
The getNeighbors(...) method now returns a List instead of an array.

Note that waiting for the fix for issue MATH-965 in Apache Commons Math
to be been officially published, a workaround has been used in Orekit.
This workaround implies that events that should be triggered based on
additional equations for integration-based propagator will be less
accurate on the first step (full accuracy is recovered once the first
step is accepted). So in these corner cases, users are advised to start
propagation at least one step before the first event (or to use a
version of Apache Commons Math that includes the fix, which has been
added to the development version as of r1465654).

This change fixes feature request #134.

Previously, they could only be used for analytical ones.

Fixes feature request #133

        simply double arrays associated to a name. They are handled
properly
        by interpolation. Note that since SpacecraftState instances are
        immutable, adding states generates a new instance, using a
fluent
        API principle (fixes feature request #132).

Fixes bug #58.