Update to resolve issue with integration-test from snapshot

[beebs-systap]

artifacts. Updated the path logic to be consistent with
AbstractDependencyMojo.

I had an issue with a JNI nar artifact that depended on a shared library nar artifact. When I ran with the locally installed version, the integration-test phase worked fine. When I deployed the shared library artifact and downloaded the dependency, the integration-test failed with the dependencies not being added.

I tracked the issue down to the version being used to add the dependency. This PR updates the NarIntegrationTestMojo dependency to be consistent with the version used in the AbstractDependencyMojo.

An example is below.

POM dependency.

                 <dependency>
                        <groupId>my.group</groupId>
                        <artifactId>shared-library</artifactId>
                        <version>1.0-SNAPSHOT</version>
                        <type>nar</type>
                </dependency>

AbstractDependencyMojo unpacks it here:

target/test-nar/shared-library-1.0-SNAPSHOT-x86_64-MacOSX-gpp-shared/lib/x86_64-MacOSX-gpp/shared

NarIntegrationTestMojo tries to find it here:

target/test-nar/shared-library-1.0-20150908.175802-15-x86_64-MacOSX-gpp-shared/lib/x86_64-MacOSX-gpp/shared

because it uses the Maven super class method version. That file doesn't exist and the library path is not modified. This update uses the getBaseVersion method instead.

[buildhive]

NAR plugin for Maven » nar-maven-plugin #363 SUCCESS
This pull request looks good
(what's this?)

[beebs-systap]

Note that this issue only occurs when the SNAPSHOT repository has the "uniqueVersion" attribute set to true.

                <snapshotRepository>
                        <id>my.snapshots</id>
                        <name>my snapshots</name>
                        <url>myurl/maven/snapshots</url>
                        <uniqueVersion>true</uniqueVersion>
                </snapshotRepository>