Mike, I think this is a great point and a great analysis.
+1 and unless anyone specifically objects I'll go ahead and do this tonight. If i run into any curveballs I'll throw it on this thread. Thanks Joe On Thu, Dec 18, 2014 at 11:04 AM, Michael Moser <[email protected]> wrote: > > I'm not sure if this is the most appropriate forum or I should have > just written a Jira ticket, but here goes. > > I believe we should consolidate the number of artifacts we have in the > nifi/commons module. We create three jars that contain just 1 class > each and there are three more jars with 3 or fewer classes in them. > This makes it annoying (especially for beginners) to find the location > of classes that you need and slightly bloats our footprint for number > of artifacts that nifi create. I believe we can improve this. > > I analyzed all of the nar-bundles to find where each common library > was used. Several are used by many framework, services, and > processors bundles already, so consolidating these common jars is a > no-brainer. Other jars that are used more sparingly contain just 1 or > 2 classes, so it really will have minimal impact to consolidate them > even if the classes aren't needed by a nar. > > So, I propose we consolidate these artifacts into the nifi-utils > artifact. The number in (parentheses) is the number of classes in > them. > > core-flowfile-attributes (2) > flowfile-packager (9) > naive-search-ring-buffer (1) > nifi-file-utils (1) > nifi-logging-utils (1) > nifi-properties (2) > nifi-security-utils (5) > nifi-socket-utils (24) > nifi-stream-utils (17) > processor-utilities (3) (this would also resolve why the name doesn't > start with "nifi") > > nifi-utils would go from 24 classes to 89 classes. > > nifi-web-utils (3), remote-communications-utils (13), and search-utils > (5) I did not include because their use is limited to just one or two > places. > > Thanks, > -- Mike >
