|
Commons Collections example source code file (compatibility.xml)
The Commons Collections compatibility.xml source code<?xml version="1.0" encoding="ISO-8859-1"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <document> <properties> <title>Compatibility <author email="dev@commons.apache.org">Commons Documentation Team </properties> <body> <section name="Version compatibility of Commons Collections"> <p> This page details the compatibility of different collections releases. </p> <p> There are two types of compatibility discussed here, source and binary. </p> <ul> <li> Two versions are source compatible when application code can be compiled against either version successfully. The compilation may result in deprecation warnings but that is perfectly acceptable. When code is source incompatible, it fails to compile, thus this type of incompatibility is easy to find. </li> <li> Two versions are binary compatible when application code compiled against one version will run using the other version without recompilation. This is much more difficult to test for, and follows quite complicated rules from the <a href="http://java.sun.com/docs/books/jls/second_edition/html/binaryComp.doc.html">Java language. </li> </ul> <p> Releases of commons collections aim to be source and binary compatible within minor versions, and to avoid breakages as much as possible between major versions. </p> <p> Commons collections 3.0 is source compatible with version 2.1 and 2.0 with the exception of classes previously deprecated in 2.0/2.1 (which were removed in 3.0). </p> <p> Commons collections 3.0 is binary compatible with version 2.1 and 2.0 <b>except for certain methods on one class. As the release was a major version, this is permitted, however it was unintentional and an error. The problem is in the <b> Other Commons Collections examples (source code examples)Here is a short list of links related to this Commons Collections compatibility.xml source code file: |
... this post is sponsored by my books ... | |
#1 New Release! |
FP Best Seller |
Copyright 1998-2024 Alvin Alexander, alvinalexander.com
All Rights Reserved.
A percentage of advertising revenue from
pages under the /java/jwarehouse
URI on this website is
paid back to open source projects.