incubator-s4-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [29/50] [abbrv] git commit: Update release notes + fix distribution build
Date Sat, 01 Jun 2013 11:33:19 GMT
Update release notes + fix distribution build


Branch: refs/heads/master
Commit: 47620a5f7929ce66176648f2837a9c2bd5475e94
Parents: 96f04a6
Author: Matthieu Morel <>
Authored: Sun Mar 10 16:51:26 2013 +0100
Committer: Matthieu Morel <>
Committed: Sun Mar 10 17:50:22 2013 +0100

 RELEASE_NOTES.html                                 |  109 +++++++--------
 build.gradle                                       |    1 +
 subprojects/s4-benchmarks/s4-benchmarks.gradle     |    1 -
 .../src/main/resources/templates/newApp.README     |    2 +-
 4 files changed, 54 insertions(+), 59 deletions(-)
diff --git a/RELEASE_NOTES.html b/RELEASE_NOTES.html
index afe12e6..c2ea03e 100644
--- a/RELEASE_NOTES.html
+++ b/RELEASE_NOTES.html
@@ -1,119 +1,114 @@
-        Release Notes - Apache S4 - Version 0.5.0
+        Release Notes - Apache S4 - Version 0.6.0
-S4 is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform

+S4 is a general-purpose, distributed, scalable, fault-tolerant, pluggable platform 
 that allows programmers to easily develop applications for processing continuous unbounded
streams of data.
-Apache S4 0.5.0 is the first release of S4 as an Apache Incubator project. 
-It is also a complete refactoring of the previous S4 codebase.
-<h2>        Sub-task
+Apache S4 0.6 contains grounds on the same basis than 0.5 and brings major performance and
usability improvements.
+<h2>        Bug
-<li>[<a href=''>S4-24</a>] -
        Dynamic deployment of S4 applications from a remote repository
-<li>[<a href=''>S4-29</a>] -
        Remove file-based configurations
-<li>[<a href=''>S4-33</a>] -
        TestUtils and modules should be split across s4-comm and s4-core
+<li>[<a href=''>S4-54</a>] -
        script can&#39;t be executed on cygwin
-<li>[<a href=''>S4-36</a>] -
        CommTests should use ZkBasedClusterManagement
+<li>[<a href=''>S4-55</a>] -
        s4-piper can‘t be executed success on cygwin
-<li>[<a href=''>S4-65</a>] -
        Create s4 status command
+<li>[<a href=''>S4-64</a>] -
        S4-piper cannot be built on RHEL 5 Linux
-<h2>        Bug
-<li>[<a href=''>S4-12</a>] -
        Dynamic Method Dispatching
+<li>[<a href=''>S4-68</a>] -
        PE Prototypes are created from a Thread with the wrong ClassLoader
-<li>[<a href=''>S4-14</a>] -
        Listener.recv() behavior when interrupted
+<li>[<a href=''>S4-90</a>] -
        &quot;unchecked or unsafe operations&quot; warning
-<li>[<a href=''>S4-18</a>] -
        gradle test fails
+<li>[<a href=''>S4-98</a>] -
        Remove duplicate Key class
-<li>[<a href=''>S4-23</a>] -
        NettyEmitter -- 1. Infinitely waiting on connection, 2. numPartitions is same as numClusterNodes
+<li>[<a href=''>S4-103</a>]
-         Inconsistent Event API on streamName/streamId
-<li>[<a href=''>S4-26</a>] -
        standalone application build script fails when the source directory contains more
than 1 class
+<li>[<a href=''>S4-105</a>]
-         Incorrect method implementation in org.apache.s4.core.Stream
-<li>[<a href=''>S4-43</a>] -
        Replace deprecated method in Gradle
+<li>[<a href=''>S4-106</a>]
-         OverloadDispatcherGenerator generates a lot of files under the /tmp folder
-<li>[<a href=''>S4-56</a>] -
        Prevent concurrent access to published s4r files
+<li>[<a href=''>S4-107</a>]
-         zkClient connect timeout when deploy application 
-<li>[<a href=''>S4-61</a>] -
        Threads running the PEs don&#39;t have a Context Class Loader
+<li>[<a href=''>S4-109</a>]
-         TCPEmitter#send() should return false when it doesn&#39;t send a packet across
-<li>[<a href=''>S4-63</a>] -
        onTime() events are not synchronized correctly
+<li>[<a href=''>S4-111</a>]
-         Deployment fails getting the .s4r file from the web
-<li>[<a href=''>S4-70</a>] -
        s4 node command ignores -zk parameter
+<li>[<a href=''>S4-112</a>]
-         Gradle doesn&#39;t resolve dependencies when they are partially in the maven
-<li>[<a href=''>S4-71</a>] -
        s4 deploy mismanages s4r URI
+<li>[<a href=''>S4-116</a>]
-         Multiple bindings of RemoteEmitters in DefaultCommModule
-<li>[<a href=''>S4-74</a>] -
        NullPointerException on TCPEmitter.onChange() 
+<li>[<a href=''>S4-120</a>]
-         User singleton scope for injections that should have a unique instance
-<li>[<a href=''>S4-82</a>] -
        Fix local communication optimization
+<li>[<a href=''>S4-123</a>]
-         Fix incomplete javadoc in AbstractSlidingWindowPE + other javadoc updates
-<li>[<a href=''>S4-87</a>] -
        Checkpointing: recovery : avoid rejections upon fetching
+<li>[<a href=''>S4-126</a>]
-         Log two times when error happens during create App
-<li>[<a href=''>S4-89</a>] -
        Fix references to S4 libs when resolving classpath for adapter in new S4 application
+<li>[<a href=''>S4-127</a>]
-         S4 status error due to invalid parsing
 <h2>        Improvement
-<li>[<a href=''>S4-6</a>] - 
       Netty initialization
+<li>[<a href=''>S4-8</a>] - 
       Blocking stream queues in cluster mode
+<li>[<a href=''>S4-48</a>] -
        When Emitter buffers fill up, enable App-specific behavior to drop/block/throttle
+<li>[<a href=''>S4-59</a>] -
        Resource loading from the S4 node classpath
-<li>[<a href=''>S4-17</a>] -
        Put tmp dir under build
+<li>[<a href=''>S4-62</a>] -
        Multithreaded Streams
-<li>[<a href=''>S4-21</a>] -
        Create standard PEs, and Event classes
+<li>[<a href=''>S4-66</a>] -
        S4R packaging: improve app class resolution
-<li>[<a href=''>S4-22</a>] -
        Adaptor + inter app communication
+<li>[<a href=''>S4-73</a>] -
        Remove appsDir concept
-<li>[<a href=''>S4-27</a>] -
        extensions to cluster configuration through Zookeeper
+<li>[<a href=''>S4-76</a>] -
        Remove unused appId identifiers
-<li>[<a href=''>S4-34</a>] -
        Rename s4.comm.netty and constituents to s4.comm.tcp
+<li>[<a href=''>S4-79</a>] -
        Validate -appClass parameter of s4r command
-<li>[<a href=''>S4-44</a>] -
        optional backoff upon multiple consecutive failed checkpoint fetches
+<li>[<a href=''>S4-94</a>] -
        Update kryo to version 2
-<li>[<a href=''>S4-57</a>] -
        Document and improve the windowing PE
+<li>[<a href=''>S4-95</a>] -
        Performance improvements
-<li>[<a href=''>S4-60</a>] -
        Development mode for rapid application development and testing
+<li>[<a href=''>S4-96</a>] -
        Log uncaught exception in spawned threads
-<li>[<a href=''>S4-67</a>] -
        S4R packaging: improve packaging of dependencies
+<li>[<a href=''>S4-99</a>] -
        Provide injectable load shedding mechanism
-<li>[<a href=''>S4-69</a>] -
        Update gradle to 1.0
+<li>[<a href=''>S4-102</a>]
-         Add facilities for accessing partition information from the application
-<li>[<a href=''>S4-72</a>] -
        Resource loading from S4R
+<li>[<a href=''>S4-108</a>]
-         Share ZooKeeper client connections from S4 nodes
-<li>[<a href=''>S4-75</a>] -
        Code improvements in comm layer
+<li>[<a href=''>S4-117</a>]
-         Improve initialization and bootstrapping
-<li>[<a href=''>S4-78</a>] -
        Gradle tasks don&#39;t finish as soon as possible
+<li>[<a href=''>S4-118</a>]
-         Check whether the app class exists when build s4r file
-<li>[<a href=''>S4-81</a>] -
        S4 tools syntax: remove curly braces + expose custom modules config
+<li>[<a href=''>S4-119</a>]
-         Publish S4 maven artifacts on public maven repository
-<li>[<a href=''>S4-85</a>] -
        Improve handling of ZK connection changes 
+<li>[<a href=''>S4-122</a>]
-         Add debug option for s4 tools
 <h2>        New Feature
-<li>[<a href=''>S4-4</a>] - 
       Dynamic App Loading
+<li>[<a href=''>S4-5</a>] - 
       Prototype app builder
-<li>[<a href=''>S4-11</a>] -
        add checkpointing mechanism to s4-piper
+<li>[<a href=''>S4-83</a>] -
        S4 command for preparing S4 projects for IDEs: eclipsify|idealize etc..
-<li>[<a href=''>S4-38</a>] -
        S4 command line utility
+<li>[<a href=''>S4-86</a>] -
 <h2>        Task
-<li>[<a href=''>S4-31</a>] -
        Facilities for packaging example and test apps
+<li>[<a href=''>S4-97</a>] -
        Add a build task for easily running Apache Creadur/Rat
-<li>[<a href=''>S4-88</a>] -
        Prepare 0.5.0 release
+<li>[<a href=''>S4-124</a>]
-         Update documentation for 0.6.0 release
\ No newline at end of file
diff --git a/build.gradle b/build.gradle
index b5428a0..00511f9 100644
--- a/build.gradle
+++ b/build.gradle
@@ -292,6 +292,7 @@ task srcDist(dependsOn: ["javadoc"], type: Zip) {
     exclude ('**/build/**')
     exclude ('**/tmp/**')
     exclude ('**/bin/**')
+    exclude ('website/**')
     into (baseName+'-'+version+'-'+classifier)
diff --git a/subprojects/s4-benchmarks/s4-benchmarks.gradle b/subprojects/s4-benchmarks/s4-benchmarks.gradle
index 222d1b4..5ed58c0 100644
--- a/subprojects/s4-benchmarks/s4-benchmarks.gradle
+++ b/subprojects/s4-benchmarks/s4-benchmarks.gradle
@@ -31,7 +31,6 @@ group = 'org.apache.s4'
 apply plugin: 'java'
 apply plugin: 'eclipse'
 apply plugin: 'idea'
-apply plugin:'application'
 /* Set Java version. */
 sourceCompatibility = 1.6
diff --git a/subprojects/s4-tools/src/main/resources/templates/newApp.README b/subprojects/s4-tools/src/main/resources/templates/newApp.README
index e572737..69975c7 100644
--- a/subprojects/s4-tools/src/main/resources/templates/newApp.README
+++ b/subprojects/s4-tools/src/main/resources/templates/newApp.README
@@ -24,7 +24,7 @@
  2. define a logical cluster for your application "./s4 newCluster -cluster=<nameOfTheCluster>
-nbTasks=<number of partitions> -flp=<a port number for the first node, other nodes
use an increment on this initial port>"
  3. start a node and attach it to the cluster "./s4 node -cluster=<nameOfTheCluster>"
  4. package the application "./s4 s4r -a=<app class> -b=`pwd`/build.gradle <package
- 5. deploy the application "./s4 deploy -s4r=`pwd`/build/libs/<package name>.s4r -c=<nameOfTheCluster>
-appName=<app name in Zookeeper>"
+ 5. deploy (configure) the application "./s4 deploy -s4r=`pwd`/build/libs/<package name>.s4r
-c=<nameOfTheCluster> -appName=<app name in Zookeeper>"
  6. check the status of the S4 cluster "s4 status"
  If you want to inject events from application 2 into application 1 on cluster 1:

View raw message