I was thinking about a build system, and the work to get there. I read YETUS-125 and the rest of the email chains.
Seems as if there is still an open discussion on whether "make" or "gradle" would fit better with the project. Might be easiest if there was first a change to the directory structure after the next release. That seems to be the most painful part, and seems like it would lend to the next step of fitting in a build system. I imagine something like this: ./src ./src/docs ./src/main ./src/main/bin ./src/main/java ./src/main/py ./src/test ./src/test/bin Not sure if it would be best to have audience annotations, and pre-commit and the others as main directories above the normal ./src directories. Would it be a good idea to open a Jira to discuss directory structure as a first start? Seems like that would be easiest to accomplish immediately after the next release. On Wed, Jun 1, 2016 at 10:36 AM, Allen Wittenauer <a...@apache.org> wrote: > > … our source could be better, but really isn’t that bad. :) We definitely > have some things to work on cleaning up though. > > I guess I should spend some time on building us a build system so that we > can run through checkstyle, etc, in the annotations bits. > > === > > For more details, see https://builds.apache.org/job/yetus-qbt/80/ > > No changes > > > > > -1 overall > > > The following subsystems voted -1: > rubocop shelldocs > > > Error Logs: > > https://builds.apache.org/job/yetus-qbt/80/artifact/out/ > diff-patch-rubocop.txt [4.0K] > https://builds.apache.org/job/yetus-qbt/80/artifact/out/ > diff-patch-ruby-lint.txt [4.0K] > https://builds.apache.org/job/yetus-qbt/80/artifact/out/ > diff-patch-shelldocs.txt [28K] > > Powered by Apache Yetus 0.4.0-SNAPSHOT http://yetus.apache.org -- Casey J. Brotherton Customer Operations Engineer [image: www.cloudera.com] <http://www.cloudera.com>
