So doubtless the cause of this is that I'm using the wrong version of *another* build tool but let's see. :)
I can't work out how the Javadocs are being kept up to date. In .gitignore in the base dir of the project we have: devel@vm17:~/incubator-samza$ tail -1 .gitignore docs/learn/documentation/0.7.0/api/javadocs Then in generate-javadocs.sh we set that directory as the destination dir: JAVADOC_DIR=$BASE_DIR/docs/learn/documentation/$VERSION/api/javadocs In that script we remove the old files, generate new ones then do a git add to add them to the set to be committed: ./gradlew javadoc rm -rf $JAVADOC_DIR mkdir -p $JAVADOC_DIR cp -r $BASE_DIR/samza-api/build/docs/javadoc/* $JAVADOC_DIR git add $JAVADOC_DIR When I run the script I get the message that nothing was added to the set due to the .gitignore entry. So how then are the Javadocs being kept up to date, the other script to publish the site doesn't include the Javadoc dir when pushing to svn? As an aside why do we have the split of Javadoc in one place and conceptually updated by one mechanism, the rest of the website content through another and svn? Thanks Garry
