You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jérôme BERNARD <je...@gmail.com> on 2005/11/18 01:09:45 UTC

surefire and systemProperties: bug?

Hi,

I am trying to specify the java.library.path property for my tests but
it seems that the following configuration does not work:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <configuration>
    <systemProperties>
      <property>
        <name>java.library.path</name>
        <value>/usr/local/lib</value>
      </property>
    </systemProperties>
  </configuration>
</plugin>

Any idea why?
I unfortunately can't rely on System.setProperty() because the
variable can be changed after initialization of the JVM but the new
value is not used at all by the JVM.

I know my java.library.path is the right one as I'm able to run my
test using IntelliJ IDEA without problem when specifying it. This is
why I suspect there is a problem with maven 2, because if the JVM is
not forked before running the tests, then the only option I have is to
run maven itselft with the correct java.library.path with is really
pity (and I have not tried this yet).

So I'm open for any suggestion :-)

Regards,
Jérôme.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: surefire and systemProperties: bug?

Posted by Brett Porter <br...@gmail.com>.
Forking support will be available in the next version.

Cheers,
Brett

On 11/18/05, Jérôme BERNARD <je...@gmail.com> wrote:
> Hi,
>
> I am trying to specify the java.library.path property for my tests but
> it seems that the following configuration does not work:
>
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-surefire-plugin</artifactId>
>   <configuration>
>     <systemProperties>
>       <property>
>         <name>java.library.path</name>
>         <value>/usr/local/lib</value>
>       </property>
>     </systemProperties>
>   </configuration>
> </plugin>
>
> Any idea why?
> I unfortunately can't rely on System.setProperty() because the
> variable can be changed after initialization of the JVM but the new
> value is not used at all by the JVM.
>
> I know my java.library.path is the right one as I'm able to run my
> test using IntelliJ IDEA without problem when specifying it. This is
> why I suspect there is a problem with maven 2, because if the JVM is
> not forked before running the tests, then the only option I have is to
> run maven itselft with the correct java.library.path with is really
> pity (and I have not tried this yet).
>
> So I'm open for any suggestion :-)
>
> Regards,
> Jérôme.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org