Set some properties for other plugins to use.

[GregDomjan]

Add some properties about what NAR has compiled/unpacked.

Mostly those related to testing the current NAR outputs come to mind, there may of course be others.

nar.library.path>target/nar/aol/shared/lib;dependency/aol/shared/lib
nar.library.path.AOL>
nar.classpath>target/classes;target/artifact.jar

To run surefire as unit tests for example

<plugin> 
  <groupId>org.apache.maven.plugins</groupId> 
  <artifactId>maven-surefire-plugin</artifactId> 
  <configuration> 
    <forkMode>once</forkMode>
    ...
    <environmentVariables> 
      <PATH>${basedir}\..;${nar.library.path}</PATH> 
    </environmentVariables> 
.. or
    <argLine>-Djava.library.path=${nar.library.path}</argLine>
    ...
  </configuration> 
</plugin> 

[dscho]

java.library.path is already set in the nar-integration-test goal... Isn't that enough for the moment?

[dscho]

In any case, I marked this post-3.0.0 because I think that we will have to be very careful what properties we want to maintain eternally...

[GregDomjan]

@dscho post-3.0.0 is fine.
While the example could be run as an integration test, there are other uses of such information that are not appropriate to run as integration test.

[GregDomjan]

The target locations can also be useful to know - have the following defined in a few projects where additional work needs to be done not covered by the NAR plugin

<nar.noarch>${project.build.directory}/nar/${project.build.finalName}-noarch</nar.noarch>
<nar.shared.x86>${project.build.directory}/nar/${project.build.finalName}-x86-Windows-msvc-shared/lib/x86-Windows-msvc/shared</nar.shared.x86>
<nar.shared.x64>${project.build.directory}/nar/${project.build.finalName}-amd64-Windows-msvc-shared/lib/x86-Windows-msvc/shared</nar.shared.x64>

[dscho]

After letting this sink for a couple of months, I think it makes a lot of sense to support this. But I lack the time to do it.

Volunteers?

[dscho]

This ticket has been open for over a year now. Can we agree that the problems are not pressing enough for anybody to take care of them? Could we therefore please agree to just close this issue, otherwise NAR plugin users might get the impression that this problem is in the process of being addressed.

[ctrueden]

Let's discuss on the maven-nar list.