Hi Again, I've moved this over to dev@
New branch with resolved discrepancies identified within release-1.5 RC1 and subsequent conversations. Branch can be seen here http://svn.apache.org/repos/asf/nutch/branches/branch-1.5/ I've also made these changes to trunk. N.B. No commits have been made in the 4 weeks since the release-1.5 RC so nothing else needs to be committed over to the new branch or forthcoming tag. I think this now paves the way for us to roll the RC taking into consideration Julien's new target. Thanks and enjoy the rest of the weekend. best Lewis On Sat, May 19, 2012 at 7:33 PM, Julien Nioche <[email protected]> wrote: >> >> 1) fix pom.xml as the versions of the deps for hadoop, tika and >> possibly others are not >> correct in the pom.xml found in the src archive and on the mvn >> repository. Are we generating the pom.xml with an Ant task? ant >> deploy? >> > > can't remember the name of the task right now but should be easy to find > out by looking at the build.xml. You'll need to make sure that the maven > tasks jars are in the lib dirr. Don't think they are there by default > > > >> 2) concerning Julien's comments w.r.t delivering the content of >> runtime/local in the >> binary archive instead of having the sources + runtime/deploy as >> well... are we near to a decision on this one? Chris, you said you are >> happy to incorporate the suggestion but this will take place @ release >> stage not before... is this an accurate description? Also Julien's >> commit to build.xml should help us out here. >> > > might as well do it in the RC to check that my changes work fine > > > >> 3) add missing license headers to the following files >> src/java/org/apache/nutch/indexer/IndexingFiltersChecker.java >> src/plugin/creativecommons/src/web/web.xml >> src/plugin/protocol-httpclient/src/test/conf/httpclient-auth-test.xml >> src/plugin/protocol-httpclient/src/test/conf/nutch-site-test.xml >> > > Hasn't this been fixed already? > > >> 4) update NOTICE file, it stated a date of 2009 >> >> So my question now... regarding making the changes which can be done >> locally e.g. 3 & 4, is it OK for me to commit to trunk? I don't know >> what the current state of play is with this and don't want to mess up >> the RC >> > > you'll probably have to redo the 1.5 branch from trunk to reflect the > latest changes > > Thanks Lewis > > J. > > > -- > * > *Open Source Solutions for Text Engineering > > http://digitalpebble.blogspot.com/ > http://www.digitalpebble.com > http://twitter.com/digitalpebble -- Lewis
