The viewerproxy.jar file no longer exists and the classes found here have been moved to the harvester.jar file. This mean all references to the viewerproxy.jarfile in manually maintained files should be replaced by a reference to the harvester.jar file (if not already included).
Indexing code merged into Harvester module
The indexing code in the archiver module has been moved to the harvester module where it logically belongs. This means that you need to update your existing deploy configurations as follows:
All overrides if any to the settings beginning with settings.archive.indexserver is to be moved to the settings.harvester.indexserver
The default indexrequestserver implementation is renamed from dk.netarkivet.archive.indexserver.distribute.IndexRequestServer to dk.netarkivet.harvester.indexserver.distribute.IndexRequestServer
The default indexClient class represented by the setting settings.common.indexClient.class is renamed from dk.netarkivet.archive.indexserver.distribute.IndexRequestClient to dk.netarkivet.harvester.indexserver.distribute.IndexRequestClient
Changes to the settings related to the harvest scheduler
The fixing of issue NAS-2069 has caused to changes to the layout of the harvester.scheduler.
Having Heritrix write warc files also requires that you add a WARCWriterProcessor to the templates you are using. We recommend that you add the following to your templates as described in the template we used in our releasetest test default_orderxml-with-source-tag-seeds-enabled.xml
This template uses as WARC writer the dk.netarkivet.harvester.harvesting.WARCWriterProcessor, which is extension of the WARCWriterProcessor bundled with Heritrix. The extension only some Netarchivesuite metadata to the WarcInfo record, so if you don't need that,you can use the class org.archive.crawler.writer.WARCWriterProcessor instead.