Inject some Verifier-like component into the scripts to ease common assertions

Some first thoughts on the API of this Asserter component:

• setCurrentDirectory(String/File path)
• assertFile(String/File path)
• assertDirectory(String/File path)
• assertNotPath(String/File path)
• assertNotPaths(String includes, String excludes)
• assertFileContents(String/File path, String encoding, String regex)

• setCurrentArchive(String/File path)
• assertArchiveEntry(String path)
• assertNotArchiveEntry(String path)
• assertNotArchiveEntries(String includes, String excludes)
• assertArchiveEntryContents(String path, String encoding, String regex)

• dispose()

The archive assertions should be reviewed to support nested archives.

setup() or initialiaze() in first ?

Not sure whether we need those. I currently have a simple/lightweight POJO class in mind (i.e. not a component in the Plexus sense) that just has some constructors for initialization and that's it. The dispose() is intended to release resources like file handles on archives. However, it's not fully thought up (at least on my side ).

To further illustrate the intended usage:

// setup the asserter for the current IT
Asserter asserter = new Asserter();
asserter.setCurrentDirectory( basedir );

// pass it on to the script interpreter as a global variable
runHookScript( ..., asserter );

// tidy up
asserter.dispose();

asserter.assertFile( "target/foo-1.0.jar" );
asserter.setCurrentDirectory( "target/exploded" );
asserter.assertFile( "WEB-INF/lib/bar-1.0.jar" );