http://git-wip-us.apache.org/repos/asf/incubator-rocketmq-site/blob/2d7f6a51/content/feed.xml ---------------------------------------------------------------------- diff --git a/content/feed.xml b/content/feed.xml new file mode 100644 index 0000000..903c0ee --- /dev/null +++ b/content/feed.xml @@ -0,0 +1,625 @@ +<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xml" href="http://localhost:4000/feed.xslt.xml";?><feed xmlns="http://www.w3.org/2005/Atom";><generator uri="http://jekyllrb.com"; version="3.3.1">Jekyll</generator><link href="http://localhost:4000/feed.xml"; rel="self" type="application/atom+xml" /><link href="http://localhost:4000/"; rel="alternate" type="text/html" /><updated>2017-03-16T11:42:05+08:00</updated><id>http://localhost:4000//</id><title type="html">Apache RocketMQ</title><subtitle>The homepage of RocketMQ.</subtitle><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"A fast, low latency, reliable, scalable, distributed MOM.", "location"=>"Hangzhou, China", "email"=>"[email protected]", "uri"=>"http://incubator.staging.apache.org/projects/rocketmq.html", "bitbucket"=>nil, "c odepen"=>nil, "dribbble"=>nil, "flickr"=>nil, "facebook"=>nil, "foursquare"=>nil, "github"=>"apache/incubator-rocketmq", "google_plus"=>nil, "keybase"=>nil, "instagram"=>nil, "lastfm"=>nil, "linkedin"=>nil, "pinterest"=>nil, "soundcloud"=>nil, "stackoverflow"=>"questions/tagged/rocketmq", "steam"=>nil, "tumblr"=>nil, "twitter"=>"ApacheRocketMQ", "vine"=>nil, "weibo"=>nil, "xing"=>nil, "youtube"=>nil, "quora"=>"topic/RocketMQ"}</name><email>[email protected]</email><uri>http://incubator.staging.apache.org/projects/rocketmq.html</uri></author><entry><title type="html">Four Methods to Feed Name Server Address List</title><link href="http://localhost:4000/ rocketmq/four-methods-to-feed-name-server-address-list/" rel="alternate" type="text/html" title="Four Methods to Feed Name Server Address List" /><published>2017-02-10T00:00:00+08:00</published><updated>2017-02-10T00:00:00+08:00</updated><id>http://localhost:4000/rocketmq/four-methods-to-feed-name-server-address-list</id><content type="html" xml:base="http://localhost:4000/rocketmq/four-methods-to-feed-name-server-address-list/";><p>In Apache RocketMQ, name servers are designed to coordinate each component of the distributed system +and fulfill much of this responsibility through managing topic route information.</p> + +<p>The management, roughly speaking, consists two parts:</p> +<ul> + <li>Brokers periodically renew meta data, including topics they have, which are kept in every name servers.</li> + <li>Name servers are serving clients, including producers, consumers and command line clients with the latest routing information.</li> +</ul> + +<p>Therefore, before launching brokers and clients, we need to tell them how to reach name servers by feeding them with a name server address list. +In Apache RocketMQ, this can be done in four ways.</p> + +<ol> + <li> + <p>Programmatic Way</p> + + <p>For broker, we may specify <code class="highlighter-rouge">namesrvAddr=name-server-ip1:port;name-server-ip2:port</code> in broker configuration file.</p> + + <p>For producers and consumers, we may feed name server address list to them as follows:</p> + + <p><code class="highlighter-rouge"> +DefaultMQProducer producer = new DefaultMQProducer("please_rename_unique_group_name"); +producer.setNamesrvAddr("name-server1-ip:port;name-server2-ip:port");</code></p> + + <p><code class="highlighter-rouge"> +DefaultMQPushConsumer consumer = new DefaultMQPushConsumer("please_rename_unique_group_name"); +consumer.setNamesrvAddr("name-server1-ip:port;name-server2-ip:port");</code></p> + + <p>If you use admin command line from shell, you may specify this way: +<code class="highlighter-rouge">sh mqadmin command-name -n name-server-ip1:port;name-server-ip2:port -X OTHER-OPTION</code></p> + + <p>a simple example is: +<code class="highlighter-rouge">sh mqadmin -n localhost:9876 clusterList</code> +assuming to query cluster info on the name server node.</p> + + <p>If integrating admin tool into your own dashboard, you may +<code class="highlighter-rouge">DefaultMQAdminExt defaultMQAdminExt = new DefaultMQAdminExt("please_rename_unique_group_name"); + defaultMQAdminExt.setNamesrvAddr("name-server1-ip:port;name-server2-ip:port");</code></p> + </li> + <li> + <p>Java Options</p> + + <p>Name server address list may also be fed to your application through specifying the sequel java option + <code class="highlighter-rouge">rocketmq.namesrv.addr</code> before launching.</p> + </li> + <li> + <p>Environment Variable</p> + + <p>You can export <code class="highlighter-rouge">NAMESRV_ADDR</code> environment variable. Brokers and clients will examine and use its value if set.</p> + </li> + <li> + <p>HTTP Endpoint</p> + + <p>If you do not specify name server address list using previously mentioned methods, Apache RocketMQ will access + the following HTTP end point to acquire and update name server address list every two minutes with initial delay of + ten seconds.</p> + + <p>On default, the end point is:</p> + + <p><code class="highlighter-rouge">http://jmenv.tbsite.net:8080/rocketmq/nsaddr</code></p> + + <p>You may override <code class="highlighter-rouge">jmenv.tbsite.net</code> by this java option: <code class="highlighter-rouge">rocketmq.namesrv.domain</code>, + You may also override <code class="highlighter-rouge">nsaddr</code> part by this java option: <code class="highlighter-rouge">rocketmq.namesrv.domain.subgroup</code></p> + + <p>If you are running Apache RocketMQ in production, this method is recommended because it gives you maximum flexibility + â you can dynamically add or remove name server nodes without necessity of rebooting your brokers and clients + according to your name serversâ system load.</p> + </li> +</ol> + +<ul> + <li> + <p>Priority</p> + + <p>Methods introduced first take precedence over the latter, namely, <br /> + <code class="highlighter-rouge">Programmatic Way &gt; Java Options &gt; Environment Variable &gt; HTTP Endpoint</code></p> + </li> +</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"A fast, low latency, reliable, scalable, distributed MOM.", "location"=>"Hangzhou, China", "email"=>"[email protected]", "uri"=>"http://incubator.staging.apache.org/projects/rocketmq.html", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, "flickr"=>nil, "facebook"=>nil, "foursquare"=>nil, "github"=>"apache/incubator-rocketmq", "google_plus"=>nil, "keybase"=>nil, "instagram"=>nil, "lastfm"=>nil, "linkedin"=>nil, "pinterest"=>nil, "soundcloud"=>nil, "stackoverflow"=>"questions/tagged/rocketmq", "steam"=>nil, "tumblr& quot;=>nil, "twitter"=>"ApacheRocketMQ", "vine"=>nil, "weibo"=>nil, "xing"=>nil, "youtube"=>nil, "quora"=>"topic/RocketMQ"}</name><email>[email protected]</email><uri>http://incubator.staging.apache.org/projects/rocketmq.html</uri></author><category term="RocketMQ" /><category term="Name Server" /><summary type="html">In Apache RocketMQ, name servers are designed to coordinate each component of the distributed system +and fulfill much of this responsibility through managing topic route information.</summary></entry><entry><title type="html">Release Notes - Apache RocketMQ - Version 4.0.0-incubating</title><link href="http://localhost:4000/release_notes/release-notes-4.0.0-incubating/"; rel="alternate" type="text/html" title="Release Notes - Apache RocketMQ - Version 4.0.0-incubating" /><published>2017-01-24T00:00:00+08:00</published><updated>2017-01-24T00:00:00+08:00</updated><id>http://localhost:4000/release_notes/release-notes-4.0.0-incubating</id><content type="html" xml:base="http://localhost:4000/release_notes/release-notes-4.0.0-incubating/";><p>Below is a summary of the JIRA issues addressed in the 4.0.0-incubating release of RocketMQ. For full documentation of the release, a guide to get started, please refer to <a href="/docs/quick-start/">Quick Start</a>.</p> + +<h2> Download the 4.0.0-incubating release +</h2> + +<ul> + <li>Source: <a href="https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip">rocketmq-all-4.0.0-incubating-source-release.zip</a> [<a href="https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.asc">PGP</a>] [<a href="https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.md5">MD5</a>] [<a href="https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-source-release.zip.sha1">SHA1</a>]</li> + <li>Binary: <a href="https://www.apache.org/dyn/closer.cgi?path=incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip">rocketmq-all-4.0.0-incubating-bin-release.zip</a> [<a href="https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.asc">PGP</a>] [<a href="https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.md5">MD5</a>] [<a href="https://www.apache.org/dist/incubator/rocketmq/4.0.0-incubating/rocketmq-all-4.0.0-incubating-bin-release.zip.sha1">SHA1</a>]</li> +</ul> + +<h2> Bug +</h2> +<ul> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-2">ROCKETMQ-2</a>] - Broker tests fail with &quot;Address + already in use&quot; + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-5">ROCKETMQ-5</a>] - Avoid creating directories in + UtilAll#getDiskPartitionSpaceUsedPercent() + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-19">ROCKETMQ-19</a>] - Thread-unsafe in + MQAdminImpl#queryMessage + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-22">ROCKETMQ-22</a>] - new funciton &#39;printWaterMark&#39; + in version 3.5.8(4.0.0) will cause a ClassCastException + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-25">ROCKETMQ-25</a>] - Query Msg by key: Possible + concurrent access to LinkedList + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-30">ROCKETMQ-30</a>] - Message Filter example has + incorrect method signature + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-31">ROCKETMQ-31</a>] - Deletion needed for + `$HOME/rmq_bk_gc.log` in `bin/mqbroker` + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-33">ROCKETMQ-33</a>] - CPU Occupy 100% + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-34">ROCKETMQ-34</a>] - Potential NPE in + NettyConnetManageHandler#connect + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-35">ROCKETMQ-35</a>] - Consumer client canât persist + consume offset table to Broker + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-45">ROCKETMQ-45</a>] - Delete consume queue hang file + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-47">ROCKETMQ-47</a>] - Broker updates NameServer + address list on startup twice + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-59">ROCKETMQ-59</a>] - Charset misusage in + RocketMQSerializable + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-64">ROCKETMQ-64</a>] - Remove duplication code line in + BrokerOuterAPI.registerBroker method + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-70">ROCKETMQ-70</a>] - Duplicate methods in + NettyRemotingClient + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-74">ROCKETMQ-74</a>] - DataVersion equals not working + as expected. + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-83">ROCKETMQ-83</a>] - Fail in quickstart-sample + </li> +</ul> + +<h2> Improvement +</h2> +<ul> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-8">ROCKETMQ-8</a>] - Standardize build script using + maven wrapper + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-11">ROCKETMQ-11</a>] - Improve concision - Reuse local + variable &#39;brokerAddrs&#39; in RouteInfoManager.getSystemTopicList method + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-14">ROCKETMQ-14</a>] - Remoting invoke callback shoule + be invoked in an executor rather than in current thread. + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-16">ROCKETMQ-16</a>] - Improve the codes of setting + topic.json&#39;s and subscriptionGroup.json&#39;s path + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-18">ROCKETMQ-18</a>] - Repackage com.alibaba to + org.apache and change maven coordinate + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-20">ROCKETMQ-20</a>] - Default &#39;consumeFromWhere&#39; + is inconsist with example&#39;s + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-29">ROCKETMQ-29</a>] - + org.apache.rocketmq.common.help.FAQUrl refers to docs in Chinese + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-32">ROCKETMQ-32</a>] - Improve concision - Reuse local + variable &#39;brokerAddrs&#39; in RouteInfoManager.getSystemTopicList method + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-37">ROCKETMQ-37</a>] - Log output information is not + accurate + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-43">ROCKETMQ-43</a>] - code style file didn&#39;t match + check-style in typecast + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-50">ROCKETMQ-50</a>] - Polish unit tests for RocketMQ + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-60">ROCKETMQ-60</a>] - Checklist review for + 4.0.0-incubating release + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-69">ROCKETMQ-69</a>] - Add link to RocketMQ web page + into README.md + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-85">ROCKETMQ-85</a>] - Polish README file and remove + all the 3rd party links in it. + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-87">ROCKETMQ-87</a>] - Polish the LICENSE and NOTICE + files to match all the dependencies + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-1">ROCKETMQ-1</a>] - Update build and clean up ip for + 4.0.0-incubating + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-38">ROCKETMQ-38</a>] - Polish unit tests for + rocketmq-remoting + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-51">ROCKETMQ-51</a>] - Polish unit tests for + rocketmq-broker + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-52">ROCKETMQ-52</a>] - Polish unit tests for + rocketmq-client + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-53">ROCKETMQ-53</a>] - Polish unit tests for + rocketmq-commons + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-54">ROCKETMQ-54</a>] - Polish unit tests for + rocketmq-namesrv + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-56">ROCKETMQ-56</a>] - Polish unit tests for + rocketmq-store + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-57">ROCKETMQ-57</a>] - Polish unit tests for + rocketmq-tools + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-58">ROCKETMQ-58</a>] - Add integration test for + RocketMQ + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-62">ROCKETMQ-62</a>] - Polish Maven assembly release + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-3">ROCKETMQ-3</a>] - Clean up the unit test of rocketmq + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-13">ROCKETMQ-13</a>] - Wrong log level for + AcceptSocketService termination + </li> + <li>[<a href="https://issues.apache.org/jira/browse/ROCKETMQ-9">ROCKETMQ-9</a>] - Errors in rocketmq-store module + </li> +</ul></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"A fast, low latency, reliable, scalable, distributed MOM.", "location"=>"Hangzhou, China", "email"=>"[email protected]", "uri"=>"http://incubator.staging.apache.org/projects/rocketmq.html", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, "flickr"=>nil, "facebook"=>nil, "foursquare"=>nil, "github"=>"apache/incubator-rocketmq", "google_plus"=>nil, "keybase"=>nil, "instagram"=>nil, "lastfm"=>nil, "linkedin"=>nil, "pinterest"=>nil, "soundcloud"=>nil, "stackoverflow"=>"questions/tagged/rocketmq", "steam"=>nil, "tumblr& quot;=>nil, "twitter"=>"ApacheRocketMQ", "vine"=>nil, "weibo"=>nil, "xing"=>nil, "youtube"=>nil, "quora"=>"topic/RocketMQ"}</name><email>[email protected]</email><uri>http://incubator.staging.apache.org/projects/rocketmq.html</uri></author><category term="Release_Notes" /><category term="RocketMQ" /><category term="Version" /><summary type="html">Below is a summary of the JIRA issues addressed in the 4.0.0-incubating release of RocketMQ. For full documentation of the release, a guide to get started, please refer to Quick Start.</summary></entry><entry><title type="html">Launch RocketMQ Code Marathon</title><link href="http://localhost:4000/activity/launch-rocketmq-code-marathon/"; rel="alternate" type="text/html" title="Launch RocketMQ Code Marathon" /><published>2017-01-05T00:00:00+08:00</published><updated>2017-01-05T00:00:00+08:00</updated><id>http://localhost:4000/ activity/launch-rocketmq-code-marathon</id><content type="html" xml:base="http://localhost:4000/activity/launch-rocketmq-code-marathon/";><p><img src="/assets/images/blog/banner.jpg" alt="Banner" /></p> +<h1 id="rocketmq-code-marathon-">ROCKETMQ CODE MARATHON <a href="/assets/attachment/launch-rocketmq-code-marathon.pdf"><i class="fa fa-link"></i></a></h1> +<h5 id="january-5th-2017">January 5th 2017</h5> + +<h2 id="objective">Objective:</h2> +<ol> + <li>Foster Community</li> + <li>Prosper Ecology</li> + <li>Incubate Committers</li> +</ol> + +<h2 id="output">Output:</h2> +<ol> + <li>1~3 Milestone Releases Per Project</li> +</ol> + +<h2 id="rewards">Rewards:</h2> +<ol> + <li>Two Potential Committers Per Project</li> + <li>Free Offers to Active Participants for On-Site Meetup</li> + <li>PMC Memberships for Qualified Committers</li> +</ol> + +<h2 id="projects">PROJECTS</h2> + +<h3 id="rocketmq-console">RocketMQ-Console</h3> +<ol> + <li>Brand New UI</li> + <li>I18n Support</li> + <li><a href="https://projects.spring.io/spring-boot/">Spring Boot</a> + <a href="http://getbootstrap.com/">Bootstrap</a> Recommended</li> + <li>Join by Creating Pull Requests against <a href="https://github.com/rocketmq/rocketmq-console-ng">RocketMQ Console Repository</a></li> +</ol> + +<h3 id="rocketmq-jms">RocketMQ-JMS</h3> +<ol> + <li>Supporting JMS 2.0 Protocol</li> + <li>Rich Documentation and Good Test Cases Coverage</li> + <li>Join by Creating Pull Requests against <a href="https://github.com/rocketmq/rocketmq-jms">RocketMQ JMS Repository</a></li> +</ol> + +<h3 id="rocketmq-flume">RocketMQ-Flume</h3> +<ol> + <li>Supporting Latest <a href="http://flume.apache.org/">Flume</a></li> + <li>Rich Documentation and Good Test Cases Coverage</li> + <li>Join by Creating Pull Requests against <a href="https://github.com/rocketmq/rocketmq-flume-ng">RocketMQ Flume Repository</a></li> +</ol></content><author><name>{"name"=>nil, "avatar"=>"/assets/images/rmq-logo.png", "bio"=>"A fast, low latency, reliable, scalable, distributed MOM.", "location"=>"Hangzhou, China", "email"=>"[email protected]", "uri"=>"http://incubator.staging.apache.org/projects/rocketmq.html", "bitbucket"=>nil, "codepen"=>nil, "dribbble"=>nil, "flickr"=>nil, "facebook"=>nil, "foursquare"=>nil, "github"=>"apache/incubator-rocketmq", "google_plus"=>nil, "keybase"=>nil, "instagram"=>nil, "lastfm"=>nil, "linkedin"=>nil, "pinterest"=>nil, "soundcloud"=>nil, "stackoverflow"=>"questions/tagged/rocketmq", "steam"=>nil, "tumblr& quot;=>nil, "twitter"=>"ApacheRocketMQ", "vine"=>nil, "weibo"=>nil, "xing"=>nil, "youtube"=>nil, "quora"=>"topic/RocketMQ"}</name><email>[email protected]</email><uri>http://incubator.staging.apache.org/projects/rocketmq.html</uri></author><category term="Activity" /><category term="Code" /><category term="Marathon" /><summary type="html">ROCKETMQ CODE MARATHON +January 5th 2017</summary></entry><entry><title type="html">Mastering Component Compatible Dependency</title><link href="http://localhost:4000/maven/mastering-component-compatible-dependency/"; rel="alternate" type="text/html" title="Mastering Component Compatible Dependency" /><published>2016-12-23T00:00:00+08:00</published><updated>2016-12-23T00:00:00+08:00</updated><id>http://localhost:4000/maven/mastering-component-compatible-dependency</id><content type="html" xml:base="http://localhost:4000/maven/mastering-component-compatible-dependency/";><p>This article mainly includes three parts.at first,I will introduce compatibility principle(more details see <a href="http://blog.csdn.net/fengjia10/article/details/7799227">here</a>) briefly.followed by a detailed elaborating about Java component compatible dependency,including the interface-oriented programming,single component signature protection,single component compatibility protection and multi-component c ompatibility compile time checking.Finally is the review and prospect,especially about <strong>Dependency Mediator</strong> project.</p> + +<aside class="sidebar__right"> +<nav class="toc"> + <header><h4 class="nav__title"><i class="fa fa-file-text"></i> On This Page</h4></header> +<ul class="toc__menu" id="markdown-toc"> + <li><a href="#compatibility" id="markdown-toc-compatibility">Compatibility</a></li> + <li><a href="#component-compatible-dependency" id="markdown-toc-component-compatible-dependency">Component Compatible Dependency</a> <ul> + <li><a href="#interface-oriented-programming" id="markdown-toc-interface-oriented-programming">Interface-oriented programming</a></li> + <li><a href="#single-component-signature-protection" id="markdown-toc-single-component-signature-protection">Single component signature protection</a></li> + <li><a href="#single-component-compatibility-protection" id="markdown-toc-single-component-compatibility-protection">Single component compatibility protection</a></li> + <li><a href="#multi-component-compatibility-compile-time-checking" id="markdown-toc-multi-component-compatibility-compile-time-checking">Multi-component compatibility compile time checking</a></li> + </ul> + </li> + <li><a href="#summary" id="markdown-toc-summary">Summary</a></li> +</ul> + + </nav> +</aside> + +<h1 id="compatibility">Compatibility</h1> + +<p>what is compatibilityï¼it is also the key to understanding the compatible dependency.Compatibility, often catch our eyes through two forms,<strong>binary compatibility</strong>,that means they can run the same executable code, typically machine code for a general purpose computer CPU.within the framework of Release-to-Release Binary Compatibility in SOM (Forman, Conner, Danforth, and Raper, Proceedings of OOPSLA â95), Java programming language binaries are binary compatible under all relevant transformations that the authors identify (with some caveats with respect to the addition of instance variables). here is a list of some important binary compatible changes that the Java programming language supports:</p> + +<ul> + <li>Reimplementing existing methods, constructors, and initializers to improve performance.</li> + <li>Changing methods or constructors to return values on inputs for which they previously either threw exceptions that normally should not occur or failed by going into an infinite loop or causing a deadlock.</li> + <li>Adding new fields, methods, or constructors to an existing class or interface.</li> + <li>Deleting private fields, methods, or constructors of a class.</li> + <li>When an entire package is updated, deleting default (package-only) access fields, methods, or constructors of classes and interfaces in the package.</li> + <li>Reordering the fields, methods, or constructors in an existing type declaration.</li> + <li>Moving a method upward in the class hierarchy.</li> + <li>Reordering the list of direct superinterfaces of a class or interface.</li> + <li>Inserting new class or interface types in the type hierarchy.</li> +</ul> + +<p>Generally,java language is <strong>upwards binary-compatible</strong> with previous version,such as Java SE 6 is upwards binary-compatible with J2SE 5.0 except for some minor incompatibilities.You can get details from <a href="http://www.oracle.com/technetwork/java/javase/compatibility-137541.html#binary">here</a>.</p> + +<p>Another compatibility form,we call it <strong>source compatibility</strong>,meaning that recompilation is necessary.Java language does not support downward source compatibility. Such as if source files use new language features or Java SE platform APIs, they will not be usable with an earlier version of the Java platform. Usually it will throw similar error like this:</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="n">java</span><span class="o">.</span><span class="na">lang</span><span class="o">.</span><span class="na">UnsupportedClassVersionError</span><span class="o">:</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">core</span><span class="o">.</span><span class="na">MessageConsumer</span> <span class="o">:</span> + <span class="n">Unsupported</span> <span class="n">major</span><span class="o">.</span><span class="na">minor</span> <span class="n">version</span> <span class="mf">51.0</span> + <span class="n">at</span> <span class="n">java</span><span class="o">.</span><span class="na">lang</span><span class="o">.</span><span class="na">ClassLoader</span><span class="o">.</span><span class="na">defineClass1</span><span class="o">(</span><span class="n">Native</span> <span class="n">Method</span><span class="o">)</span> + <span class="n">at</span> <span class="n">java</span><span class="o">.</span><span class="na">lang</span><span class="o">.</span><span class="na">ClassLoader</span><span class="o">.</span><span class="na">defineClassCond</span><span class="o">(</span><span class="n">Unknown</span> <span class="n">Source</span><span class="o">)</span> +</code></pre> +</div> + +<p>Java language source compatibility policy is as follows,except for any incompatibilities listed further below:</p> + +<ul> + <li>Maintenance releases (such as 1.7.25, 1.7.26) do not introduce any new language features or APIs. They will maintain source-compatibility with each other.</li> + <li>Functionality releases and major releases (such as 1.4.0,5.0,6.0,7.0,8.0) maintain upwards but not downwards source-compatibility.</li> +</ul> + +<p>Letâs sum up before going on:</p> + +<ul> + <li>Document those incompatibility cases as much as possible, even some rare circumstances and corner cases.</li> + <li>Recommend developer to provide facilities that alert developers to the impact of changes on pre-existing binaries that cannot be recompiled.</li> + <li>Generally speaking,Binary Compatibility problems may occur in the following situations:</li> + <li><strong>Replacing the old with the new</strong>,such as the Java platform Profiling Architecture in the Java SE6,JVMDI was removed and JVMPI was disabled in Java SE 6.</li> + <li><strong>Combinatorial resolution</strong>,such as Non class files have been moved from rt.jar in Java SE 6.if -Xbootclasspath:<path to="" rt.jar=""> is specified,and request any resource files will fail since these resources now reside in a different jar file called resources.jar.</path></li> + <li><strong>Behavior change</strong>,such as Java SE 6 will throw an OverlappingFileLockException,if the application attempts to lock the overlapping region other instances of FileChannel that has been locked, in order to realize the backward compatibility, it provides disableSystemWideOverlappingFileLockCheck system properties. again, also in Java SE 6, jar will preserve file modification dates and times during extract, through the sun.tools.jar.useExtractionTime=true to achieve backward compatibility.</li> + <li><strong>Structure change</strong>,this is also the key problem to solve in <strong>Dependency Mediator</strong> project. generally speaking,modification and deletion belonging to incompatible operations.and more attentions must be paid in the RPC service maintenance, more detailed description,please refer to an <a href="http://blog.csdn.net/fengjia10/article/details/7799227">article</a> I wrote before. also you can read the the thirteenth chapter of Java language specification.</li> +</ul> + +<h1 id="component-compatible-dependency">Component Compatible Dependency</h1> + +<p>This article donât talk about <strong>dependency analysis</strong> and <strong>dependency decoupling</strong>,if you care these topics,please read <a href="http://java.dzone.com/articles/dependency-analysis-and-1">Dependency Analysis and the Modularisation of Java Programs</a>.highly recommending you try to dive into open source project <a href="http://xplrarc.massey.ac.nz/">Architecture Explorer</a>,through bcel technology,analyzing and measuring componentâs dependency relationship.but in my opinion,<a href="http://clarkware.com/software/JDepend.html">Jdepend</a> was surely the most distinguished tool in dependency analysis and dependency decoupling area.it traverses Java class file directories and generates design quality metrics for each Java package,also allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability t o manage package dependencies effectively.</p> + +<p>Letâs return,ask yourselfï¼have you ever been disturbed by the following problems?</p> + +<ul> + <li>Your service depend a volatile service,volatile means your service depending neither an abstract class nor a interface,this class update at irregular intervals,you often encountered errors such as <strong>NoSuchMethodError</strong>,<strong>NoSuchFieldError</strong> and <strong>NoClassDefFoundError</strong> etc.</li> + <li>You are developing a new feature,but this feature can not backward compatible with previous version, +what should you do ? How do you give a incompatible list in your release report.</li> + <li>Java language library is a superb collection of beautiful things,how do you make a rational dependency exclusion and effective mediate various dependency problems when developing.</li> +</ul> + +<p>It is the time to introduce the key idea - <strong>Mediating Components Compatible Dependency</strong>.Specifically,it includs the following basic principles:</p> + +<ul> + <li>Interface-oriented programming</li> + <li>Single component signature protection</li> + <li>Single component compatibility protection</li> + <li>Multi-component compatibility compile time checking</li> +</ul> + +<h2 id="interface-oriented-programming">Interface-oriented programming</h2> + +<p>Interface-oriented programming,Itâs easier said than done.I will cite SLF4J design philosophy explain this principle.</p> + +<p>Differing from commons logging,SLF4J use <strong>static binder technology</strong> so as to avoid notorious <a href="http://articles.qos.ch/classloader.html">classloader problem</a>,every concrete log implementation must +have a class named StaticLoggerBinder and implementing SLF4J spi LoggerFactoryBinder.thus you just depend SLF4J api,not concerned about underlying implementation.some people may asking,why choose SLF4J not commons loggingï¼I can also depend commons logging api but not concret implementationï¼itâs not performance but classloader problem.JCL discovery process relies on classloader hacks to find the logging framework at runtime but this mechanism leads to numerous problems including unexpected behavior,hard to debug classloading problems resulting in increased complexity.This is nicely captured by Ceki (the author of Log4J, SLF4J and Logback) in Think again before adopting the commons-logging API (which also mentions memory leaks problems observed with JCL).and this is why SLF4J, which uses static bindings, has been created. Letâs see.how to find the concrete realizations in SLF4J:</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="c1">// We need to use the name of the StaticLoggerBinder class, but we can't reference</span> +<span class="c1">// the class itself.</span> +<span class="kd">private</span> <span class="kd">static</span> <span class="n">String</span> <span class="n">STATIC_LOGGER_BINDER_PATH</span> <span class="o">=</span> <span class="s">"org/slf4j/impl/StaticLoggerBinder.class"</span><span class="o">;</span> + <span class="cm">/** + * It is LoggerFactory's responsibility to track version changes and manage + * the compatibility list. + * It is assumed that all versions in the 1.6 are mutually compatible. + */</span> +<span class="kd">static</span> <span class="kd">private</span> <span class="kd">final</span> <span class="n">String</span><span class="o">[]</span> <span class="n">API_COMPATIBILITY_LIST</span> <span class="o">=</span> <span class="k">new</span> <span class="n">String</span><span class="o">[]{</span><span class="s">"1.6"</span><span class="o">,</span> <span class="s">"1.7"</span><span class="o">};</span> + +<span class="c1">// private constructor prevents instantiation</span> +<span class="kd">private</span> <span class="nf">LoggerFactory</span><span class="o">()</span> <span class="o">{}</span> +<span class="kd">private</span> <span class="kd">final</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">versionSanityCheck</span><span class="o">()</span> <span class="o">{</span> + <span class="k">try</span> <span class="o">{</span> + <span class="n">String</span> <span class="n">requested</span> <span class="o">=</span> <span class="n">StaticLoggerBinder</span><span class="o">.</span><span class="na">REQUESTED_API_VERSION</span><span class="o">;</span> + <span class="kt">boolean</span> <span class="n">match</span> <span class="o">=</span> <span class="kc">false</span><span class="o">;</span> + <span class="k">for</span> <span class="o">(</span><span class="kt">int</span> <span class="n">i</span> <span class="o">=</span> <span class="mi">0</span><span class="o">;</span> <span class="n">i</span> <span class="o">&lt;</span> <span class="n">API_COMPATIBILITY_LIST</span><span class="o">.</span><span class="na">length</span><span class="o">;</span> <span class="n">i</span><span class="o">++)</span> <span class="o">{</span> + <span class="k">if</span> <span class="o">(</span><span class="n">requested</span><span class="o">.</span><span class="na">startsWith</span><span class="o">(</span><span class="n">API_COMPATIBILITY_LIST</span><span class="o">[</span><span class="n">i</span><span class="o">]))</span> <span class="o">{</span> + <span class="n">match</span> <span class="o">=</span> <span class="kc">true</span><span class="o">;</span> + <span class="o">}</span> + <span class="o">}</span> + <span class="k">if</span> <span class="o">(!</span><span class="n">match</span><span class="o">)</span> <span class="o">{</span> + <span class="n">Util</span><span class="o">.</span><span class="na">report</span><span class="o">(</span><span class="s">"The requested version "</span> <span class="o">+</span> <span class="n">requested</span> + <span class="o">+</span> <span class="s">" by your slf4j binding is not compatible with "</span> + <span class="o">+</span> <span class="n">Arrays</span><span class="o">.</span><span class="na">asList</span><span class="o">(</span><span class="n">API_COMPATIBILITY_LIST</span><span class="o">).</span><span class="na">toString</span><span class="o">());</span> + <span class="n">Util</span><span class="o">.</span><span class="na">report</span><span class="o">(</span><span class="s">"See "</span> <span class="o">+</span> <span class="n">VERSION_MISMATCH</span> <span class="o">+</span> <span class="s">" for further details."</span><span class="o">);</span> + <span class="o">}</span> +<span class="o">}</span> <span class="k">catch</span> <span class="o">(</span><span class="n">java</span><span class="o">.</span><span class="na">lang</span><span class="o">.</span><span class="na">NoSuchFieldError</span> <span class="n">nsfe</span><span class="o">)</span> <span class="o">{</span> + <span class="c1">// given our large user base and SLF4J's commitment to backward</span> + <span class="c1">// compatibility, we cannot cry here. Only for implementations</span> + <span class="c1">// which willingly declare a REQUESTED_API_VERSION field do we</span> + <span class="c1">// emit compatibility warnings.</span> +<span class="o">}</span> <span class="k">catch</span> <span class="o">(</span><span class="n">Throwable</span> <span class="n">e</span><span class="o">)</span> <span class="o">{</span> + <span class="c1">// we should never reach here</span> + <span class="n">Util</span><span class="o">.</span><span class="na">report</span><span class="o">(</span><span class="s">"Unexpected problem occured during version sanity check"</span><span class="o">,</span> <span class="n">e</span><span class="o">);</span> + <span class="o">}</span> +<span class="o">}</span> +</code></pre> +</div> + +<p>you can use these skills at your library.just Let others depend on your interface package,detecting certain implementation statically.</p> + +<p>If you have developed an old version library,naming it as 2.x.x.next version,you hope to refactor some implementations,how to process multi-version compatibility?here is a skill from maven dependency plugin:</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="n">String</span> <span class="n">hint</span> <span class="o">=</span> <span class="n">isMaven31</span><span class="o">()</span> <span class="o">?</span> <span class="s">"maven31"</span> <span class="o">:</span> <span class="n">isMaven2x</span><span class="o">()</span> <span class="o">?</span> <span class="s">"maven2"</span> <span class="o">:</span> <span class="s">"maven3"</span><span class="o">;</span> + +<span class="cm">/** +* Check the current Maven version to see if it's Maven 2.x. +*/</span> +<span class="kd">protected</span> <span class="kd">static</span> <span class="kt">boolean</span> <span class="nf">isMaven2x</span><span class="o">()</span> +<span class="o">{</span> + <span class="k">return</span> <span class="o">!</span><span class="n">canFindCoreClass</span><span class="o">(</span> <span class="s">"org.apache.maven.project.DependencyResolutionRequest"</span> <span class="o">);</span> <span class="c1">// Maven 3 specific</span> +<span class="o">}</span> + +<span class="cm">/** +* Check the current Maven version to see if it's Maven 3.1. +*/</span> +<span class="kd">protected</span> <span class="kd">static</span> <span class="kt">boolean</span> <span class="nf">isMaven31</span><span class="o">()</span> +<span class="o">{</span> + <span class="k">return</span> <span class="nf">canFindCoreClass</span><span class="o">(</span> <span class="s">"org.eclipse.aether.artifact.Artifact"</span> <span class="o">);</span> <span class="c1">// Maven 3.1 specific</span> +<span class="o">}</span> +</code></pre> +</div> + +<h2 id="single-component-signature-protection">Single component signature protection</h2> + +<p>Secondly,Single component signature protection,you can using <a href="http://mojo.codehaus.org/animal-sniffer/">Animal Sniffer project</a> as well-known Guava library,Animal Sniffer provides tools to assist verifying that classes compiled with a newer JDK/API are compatible with an older JDK/API.</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="o">&lt;</span><span class="n">plugin</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">groupId</span><span class="o">&gt;</span><span class="n">org</span><span class="o">.</span><span class="na">codehaus</span><span class="o">.</span><span class="na">mojo</span><span class="o">&lt;/</span><span class="n">groupId</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">artifactId</span><span class="o">&gt;</span><span class="n">animal</span><span class="o">-</span><span class="n">sniffer</span><span class="o">-</span><span class="n">maven</span><span class="o">-</span><span class="n">plugin</span><span class="o">&lt;/</span><span class="n">artifactId</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">configuration</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">signature</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">groupId</span><span class="o">&gt;</span><span class="n">org</span><span class="o">.</span><span class="na">codehaus</span><span class="o">.</span><span class="na">mojo</span><span class="o">.</span><span class="na">signature</span><span class="o">&lt;/</span><span class="n">groupId</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">artifactId</span><span class="o">&gt;</span><span class="n">java16</span><span class="o">-</span><span class="n">sun</span><span class="o">&lt;/</span><span class="n">artifactId</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">version</span><span class="o">&gt;</span><span class="mf">1.0</span><span class="o">&lt;/</span><span class="n">version</span><span class="o">&gt;</span> + <span class="o">&lt;/</span><span class="n">signature</span><span class="o">&gt;</span> + <span class="o">&lt;/</span><span class="n">configuration</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">executions</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">execution</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">id</span><span class="o">&gt;</span><span class="n">check</span><span class="o">-</span><span class="n">java16</span><span class="o">-</span><span class="n">sun</span><span class="o">&lt;/</span><span class="n">id</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">phase</span><span class="o">&gt;</span><span class="n">test</span><span class="o">&lt;/</span><span class="n">phase</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">goals</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">goal</span><span class="o">&gt;</span><span class="n">check</span><span class="o">&lt;/</span><span class="n">goal</span><span class="o">&gt;</span> + <span class="o">&lt;/</span><span class="n">goals</span><span class="o">&gt;</span> + <span class="o">&lt;/</span><span class="n">execution</span><span class="o">&gt;</span> + <span class="o">&lt;/</span><span class="n">executions</span><span class="o">&gt;</span> + <span class="o">&lt;/</span><span class="n">plugin</span><span class="o">&gt;</span> +</code></pre> +</div> + +<p>So from now on, when you performing a mvn test or mvn install operation. If there is an incompatibility in one of the projects, you would find some output like this:</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="o">[</span><span class="n">INFO</span><span class="o">]</span> <span class="o">[</span><span class="n">animal</span><span class="o">-</span><span class="nl">sniffer:</span><span class="n">check</span> <span class="o">{</span><span class="nl">execution:</span> <span class="n">check</span><span class="o">-</span><span class="n">java</span><span class="o">-</span><span class="n">api</span><span class="o">}]</span> +<span class="o">[</span><span class="n">INFO</span><span class="o">]</span> <span class="n">Checking</span> <span class="n">unresolved</span> <span class="n">references</span> <span class="n">to</span> <span class="n">org</span><span class="o">.</span><span class="na">codehaus</span><span class="o">.</span><span class="na">mojo</span><span class="o">.</span><span class="na">signature</span><span class="o">:</span><span class="n">java16</span><span class="o">-</span><span class="nl">sun:</span><span class="mf">1.0</span> +<span class="o">[</span><span class="n">ERROR</span><span class="o">]</span> <span class="n">Undefined</span> <span class="nl">reference:</span> <span class="n">java</span><span class="o">/</span><span class="n">lang</span><span class="o">/</span><span class="n">String</span><span class="o">.</span><span class="na">contains</span><span class="o">(</span><span class="n">Ljava</span><span class="o">/</span><span class="n">lang</span><span class="o">/</span><span class="n">CharSequence</span><span class="o">;)</span><span class="n">Z</span> <span clas s="n">in</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">admin</span><span class="o">/</span><span class="n">workspace</span><span class="o">/</span><span class="n">kafka</span><span class="o">/</span><span class="n">target</span><span class="o">/</span><span class="n">classes</span><span class="o">/</span><span class="n">org</span><span class="o">/</span><span class="n">kafka</span><span class="o">/</span><span class="n">tools</span><span class="o">...</span><span class="na">Producer</ span><span class="o">.</span><span class="na">class</span> +</code></pre> +</div> + +<p>More details please see <a href="http://blog.gvsig.org/2011/07/25/hunting-api-incompatibilities-with-the-animal-sniffer-project/">here</a>.</p> + +<h2 id="single-component-compatibility-protection">Single component compatibility protection</h2> + +<p>If your a SOA develper,you almost concerned with single component compatibility protection.[Clirr project] (http://clirr.sourceforge.net/) may be your best choice.Clirr is a tool that checks Java libraries for binary and source compatibility with older releases. Basically you give it two sets of jar files and Clirr dumps out a list of changes in the public api. The Clirr Ant task can be configured to break the build if it detects incompatible api changes. In a continuous integration process Clirr can automatically prevent accidental introduction of binary or source compatibility problems.</p> + +<p>How to use itï¼just add some config snippets in your pom :</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="o">&lt;</span><span class="n">plugin</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">groupId</span><span class="o">&gt;</span><span class="n">org</span><span class="o">.</span><span class="na">codehaus</span><span class="o">.</span><span class="na">mojo</span><span class="o">&lt;/</span><span class="n">groupId</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">artifactId</span><span class="o">&gt;</span><span class="n">clirr</span><span class="o">-</span><span class="n">maven</span><span class="o">-</span><span class="n">plugin</span><span class="o">&lt;/</span><span class="n">artifactId</span><span class="o">&gt;</span> + <span class="o">&lt;</span><span class="n">version</span><span class="o">&gt;</span><span class="mf">2.6</span><span class="o">.</span><span class="mi">1</span><span class="o">&lt;/</span><span class="n">version</span><span class="o">&gt;</span> +<span class="o">&lt;/</span><span class="n">plugin</span><span class="o">&gt;</span> +</code></pre> +</div> + +<p>then,run <code class="highlighter-rouge">mvn clirr:check</code>,output may be like this:</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="o">[</span><span class="n">INFO</span><span class="o">]</span> <span class="o">---</span> <span class="n">clirr</span><span class="o">-</span><span class="n">maven</span><span class="o">-</span><span class="nl">plugin:</span><span class="mf">2.6</span><span class="o">.</span><span class="mi">1</span><span class="o">:</span><span class="n">check</span> <span class="o">(</span><span class="k">default</span><span class="o">-</span><span class="n">cli</span><span class=&qu ot;o">)</span> <span class="err">@</span> <span class="n">cmq</span><span class="o">.</span><span class="na">common</span> <span class="o">---</span> +<span class="o">[</span><span class="n">INFO</span><span class="o">]</span> <span class="n">artifact</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">intl</span><span class="o">.</span><span class="na">base</span><span class="o">.</span><span class="na">cmq</span><span class="o">:</span><span class="n">cmq</span><span class="o">.</span><span class="na">common</span><span class="o">:</span> <span class="n">checking</span> <span class="k">for</span> <span class="n&qu ot;>updates</span> <span class="n">from</span> <span class="n">b2bmirror</span><span class="o">-</span><span class="n">all</span> +<span class="o">[</span><span class="n">INFO</span><span class="o">]</span> <span class="n">Comparing</span> <span class="n">to</span> <span class="nl">version:</span> <span class="mf">2.0</span><span class="o">.</span><span class="mi">1</span> +<span class="o">[</span><span class="n">ERROR</span><span class="o">]</span> <span class="mi">7005</span><span class="o">:</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">client</span><span class="o">.</span><span class="na">CompletionListener</span><span class="o">:</span> <span class="n">Parameter</span> <span class="mi">1</span> <span class="n">of</span> <span class="err">'</span><span class="kd">public</span> <span class="kt">void</span> <span class="nf">onCompletion</span><span class="o">(</span><span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">model</span><span class="o">.</span><span class="na">CommonMessage</span><span class="o">)</span><span class="err">'</span> <span class="n">has</span> <span class="n">changed</span> <span class="n">its</span> <span class="n">type</span> <span class="n">to</span> <span class="n">com</span><span class ="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">common</span><span class="o">.</span><span class="na">CommonMessage</span> +<span class="o">[</span><span class="n">ERROR</span><span class="o">]</span> <span class="mi">7005</span><span class="o">:</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">client</span><span class="o">.</span><span class="na">CompletionListener</span><span class="o">:</span> <span class="n">Parameter</span> <span class="mi">1</span> <span class="n">of</span> <span class="err">'</span><span class="kd">public</span> <span class="kt">void</span> <span class="nf">onException</span><span class="o">(</span><span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">model</span><span class="o">.</span><span class="na">CommonMessage</span><span class="o">,</span> <span class="n">java</span><span class="o">.</span><span class="na">lang</span><span class="o">.</span><span class="na">Exception</span><span class="o">)</span><span class="err">'</span> <span class=" n">has</span> <span class="n">changed</span> <span class="n">its</span> <span class="n">type</span> <span class="n">to</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">common</span><span class="o">.</span><span class="na">CommonMessage</span> +<span class="o">[</span><span class="n">ERROR</span><span class="o">]</span> <span class="mi">7005</span><span class="o">:</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">client</span><span class="o">.</span><span class="na">MessageProducer</span><span class="o">:</span> <span class="n">Parameter</span> <span class="mi">1</span> <span class="n">of</span> <span class="err">'</span><span class="kd">public</span> <span cla ss="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">client</span><span class="o">.</span><span class="na">CommonResult</span> <span class="nf">send</span><span class="o">(</span><span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">model</span><span class="o">.</span><span class="na">CommonMessage</span><span class="o&quo t;>)</span><span class="err">'</span> <span class="n">has</span> <span class="n">changed</span> <span class="n">its</span> <span class="n">type</span> <span class="n">to</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">common</span><span class="o">.</span><span class="na">CommonMessage</span> +<span class="o">[</span><span class="n">ERROR</span><span class="o">]</span> <span class="mi">7005</span><span class="o">:</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">client</span><span class="o">.</span><span class="na">MessageProducer</span><span class="o">:</span> <span class="n">Parameter</span> <span class="mi">1</span> <span class="n">of</span> <span class="err">'</span><span class="kd">public</span> <span cla ss="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">client</span><span class="o">.</span><span class="na">CommonResult</span> <span class="nf">send</span><span class="o">(</span><span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">model</span><span class="o">.</span><span class="na">CommonMessage</span><span class="o&quo t;>,</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.</span><span class="na">mq</span><span class="o">.</span><span class="na">client</span><span class="o">.</span><span class="na">CompletionListener</span><span class="o">)</span><span class="err">'</span> <span class="n">has</span> <span class="n">changed</span> <span class="n">its</span> <span class="n">type</span> <span class="n">to</span> <span class="n">com</span><span class="o">.</span><span class="na">alibaba</span><span class="o">.< ;/span><span class="na">mq</span><span class="o">.</span><span class="na">common</span><span class="o">.</span><span class="na">CommonMessage</span> +</code></pre> +</div> + +<p>Some inspiration in <strong>Dependency Mediator</strong> project just come from here.more topics about compatible,you can reference from series article <a href="http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs">Evolving Java-based APIs</a></p> + +<h2 id="multi-component-compatibility-compile-time-checking">Multi-component compatibility compile time checking</h2> + +<p>Last but not least,Multi-component compatibility compile time checking.itâs the time to formally recommend project <strong>Dependency Mediator</strong>.</p> + +<p>unlike karaf and other lightness modular technology(like osgi,class names do not need to be unique,but the combination of class names and their defining ClassLoader must to be unique),<strong>Dependency Mediator</strong> try to remedy component dependency conflicting problem before the runtime rather than using customized <a href="http://www.onjava.com/pub/a/onjava/2005/04/13/dependencies.html">classLoader</a> to agree with the coexistence of different version components,thus avoid some well-konwn errors,such as <strong>NoSuchMethodError</strong>,<strong>NoSuchFieldError</strong> and <strong>NoClassDefFoundError</strong> etc.</p> + +<p>What is the principle of <strong>Dependency Mediator</strong>ï¼<strong>Dependency Mediator</strong> try to mediate various component conflicting problems.It uses jar or class as the smallest component unit,that is ComponentEntry:</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="kd">public</span> <span class="kd">class</span> <span class="nc">ComponentEntry</span> <span class="kd">implements</span> <span class="n">Comparable</span><span class="o">&lt;</span><span class="n">ComponentEntry</span><span class="o">&gt;</span> <span class="o">{</span> + <span class="cm">/** + * Similar file name + */</span> + <span class="kd">private</span> <span class="n">String</span> <span class="n">pathName</span><span class="o">;</span> + <span class="cm">/** + * Component name ,such as fully-qualified class name or jar name + */</span> + <span class="kd">private</span> <span class="n">String</span> <span class="n">name</span><span class="o">;</span> + <span class="cm">/** + * Name of the jar which contains this entry,this field may be null + */</span> + <span class="kd">private</span> <span class="n">String</span> <span class="n">jarName</span><span class="o">;</span> + <span class="cm">/** + * Jar entry meta info,if it is a jar file,this field may be null + */</span> + <span class="kd">private</span> <span class="n">JarEntry</span> <span class="n">entry</span><span class="o">;</span> + <span class="o">....</span> +</code></pre> +</div> + +<p>It could scan directory(also including classpath,if you set system property scanClasspath) and POM.if it happen to jar,but you setting checkJars to false,it could detect inner MANIFEST file,using <strong>Build-Jdk</strong> and <strong>Built-By</strong> properties to decide whether duplicated jars.thus,output only report whether including duplicated jar.but if you +setting checkJars to true or nothing to do with this property,it will further analyzes whether existing incompatible cases.</p> + +<p>It also provides a maven plugin,if your project is a web project,you must run mvn insall before next step. Maven plugin also comply with the latest annotation mojo api rather than version 2.x.x doclet api.</p> + +<p><strong>Dependency Mediator</strong> take advantage of <strong>nearest definition</strong> dependency mediation strategy. this determines what version of a dependency will be used when multiple versions of an artifact are encountered. <strong>nearest definition</strong>,means that it will use the version of the closest dependency to your project in the tree of dependencies. You can always guarantee a version by declaring it explicitly in your projectâs POM. Note that if two dependency versions are at the same depth in the dependency tree, until Maven 2.0.8 it was not defined which one would win, but since Maven 2.0.9 itâs the order in the declaration that counts: the first declaration wins. +<strong>nearest definition</strong> means that the version used will be the closest one to your project in the tree of dependencies, eg. if dependencies for A, B, and C are defined as A -&gt; B -&gt; C -&gt; D 2.0 and A -&gt; E -&gt; D 1.0, then D 1.0 will be used when building A because the path from A to D through E is shorter. You could explicitly add a dependency to D 2.0 in A to force the use of D 2.0.</p> + +<p>If you consider the dependency hierarchy as a binary tree structure,Undoubtedly,<strong>nearest definition</strong> means the <strong>minimum depth</strong>. so if you put some higher version dependency library after lower version one(may be transitive dependency),you will face incompatible conflicting problems.Such as :</p> + +<div class="language-java highlighter-rouge"><pre class="highlight"><code><span class="o">[</span><span class="n">WARNING</span><span class="o">]</span> <span class="n">Founded</span> <span class="n">conflicting</span> <span class="n">dependency</span> <span class="nl">component:</span><span class="n">org</span><span class="o">.</span><span class="na">apache</span><span class="o">.</span><span class="na">thrift</span><span class="o">:</span><span class="nl">libthrift:</span><span class="n">jar</span> <span class="n">Resolved</span> <span class="n">version</span> <span class=& quot;n">is</span> <span class="n">org</span><span class="o">.</span><span class="na">apache</span><span class="o">.</span><span class="na">thrift</span><span class="o">:</span><span class="nl">libthrift:jar:</span><span class="mf">0.8</span><span class="o">.</span><span class="mi">0</span><span class="o">:</span><span class="n">compile</span> <span class="n">But</span> <span class="n">found</span> <span class="n">conflicting</span> <span class="n">artifact</span> <span class="n">org</span><span class="o">.</span><span class="na">apache</span><span class=&q uot;o">.</span><span class="na">thrift</span><span class="o">:</span><span class="nl">libthrift:</span><span class="mf">0.9</span><span class="o">.</span><span class="mi">1</span> +</code></pre> +</div> + +<p>In this case,you could fix this problem through place libthrift 0.9.1 before the library imported through transitive dependency.</p> + +<p>of course,all the establishment must meet a premise,that is:</p> +<ul> + <li><strong>Functionality releases and major releases(such as 1.4.x, 1.5.x,2.x.x,3.x.x) have source compatibility problems.</strong></li> +&l
<TRUNCATED>
