[Netarchivesuite-users] Netarchivesuite development status before summer vacation

[Mikis Seth Sørensen]

Hi all

Here is a short update on the development status of Netarchivesuite. The past couple of months has been dedicated to modernizing the NetarchiveSuite codebase and development environment setup. Så the current state of affairs are:

 *   The codebase has been moved to Github and can now be found here: https://github.com/netarchivesuite/netarchivesuite. New guidelines for working with the repository is available here: https://sbforge.org/display/NAS/Contributing+code+to+NetarchiveSuite. This resolves NAS-2041<https://sbforge.org/jira/browse/NAS-2041> Switch to git as the NetarchiveSuite SCM<https://sbforge.org/jira/browse/NAS-2041>.
 *   The build is now Maven based, which has imposed quite a lot structural changes to the src code to comply with Mavens strict module model. Most of the test code has being moved into separate test modules, where we have started a effort to have a cleaner separation between pure unit tests and integration tests. There is still a lot of cleanup work to do, especially to cleanup the ‘unclassified folder, which contains the files and folders which couldn’t initially find a home in the new Maven based structure. This resolves NAS-8<https://sbforge.org/jira/browse/NAS-8> Switch to Maven as build tool.
 *   The process of switching from JUnit3 to JUnit4 has started, see NAS-2312<https://sbforge.org/jira/browse/NAS-2312> Migrate current JUnit3 tests to JUnit4.
 *   All test DB usage gas changed from using prepackaged Derby DB snapshots to generate the databases on the fly from the pure DB creating schema + population sql statements. This resolved NAS-2339<https://sbforge.org/jira/browse/NAS-2339> Create SQL scripts equivalent to existing binary database jars and contributes to NAS-2297<https://sbforge.org/jira/browse/NAS-2297> Remove usage of custom DB dumps for Quickstart and test databases. This is part of the greater effort to drop having to support Derby altogether, see NAS-2268<https://sbforge.org/jira/browse/NAS-2268> Switch to H2 as test DB<https://sbforge.org/jira/browse/NAS-2268>.
 *   Work on switching to slf4j as the logging api is nearly finished, see
 *   NAS-2124<https://sbforge.org/jira/browse/NAS-2124>
Switch to slf4j as logging framework
 *   We have being looking a bit at how we can consolidate our code style, which have been documented here: https://sbforge.org/display/NAS/Coding+Guidelines.

So the next step is to verify the system still works correctly after all the changes by running a release test in the beginning of august, see https://sbforge.org/display/NAS/5.0-Milestone1+release+test. Not too many problems should appear here, as the system test is running and is green, see https://sbforge.org/jenkins/view/NetarchiveSuite/job/NetarchiveSuite-nightly-systemtest/.

After this the focus will shift to the Heritrix 3 adoption, https://sbforge.org/jira/browse/NAS-1780, while work on consolidation the modernization effort continuos.

Have a nice summer
The DK NetarchiveSuite Team.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.sbforge.org/pipermail/netarchivesuite-users/attachments/20140709/f2e074f9/attachment.html>