jna.nosys=true and setting java system properties in general...

1,146 views
Skip to first unread message

Jim Hargrave

unread,
May 30, 2013, 12:13:34 PM5/30/13
to okapi...@googlegroups.com
I decided to add the jna.nosys option to the super pom so that any
future project added will avoid the problems with the tmp files on
multiuser system. Also you can set other system properties in the plugin
so they are available to the build. The cost is one more maven plugin to
download, but who will notice :-)

I tested by making my /tmp/jna owner "root" then running a full build as
another user. No build errors. I will test this on my work machine as well.

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>properties-maven-plugin</artifactId>
<version>1.0-alpha-2</version>
<executions>
<execution>
<goals>
<goal>set-system-properties</goal>
</goals>
<configuration>
<properties>
<property>
<name>jna.nosys</name>
<value>true</value>
</property>
</properties>
</configuration>
</execution>
</executions>
</plugin>

Yves Savourel

unread,
May 30, 2013, 5:28:21 PM5/30/13
to okapi...@googlegroups.com
> I tested by making my /tmp/jna owner "root" then running
> a full build as another user. No build errors.
> I will test this on my work machine as well.
> ...
> ...The cost is one more maven plugin to download,
> but who will notice :-)

Sir Jenkins took notice and obviously found a way to show its irritation:
https://okapi.ci.cloudbees.com/job/okapi/860/

Likely it's one of those moody errors, that will resolve itself at the next build.

-ys

Jim Hargrave

unread,
May 30, 2013, 6:03:39 PM5/30/13
to okapi...@googlegroups.com, Yves Savourel
Build #861 was successful - maybe Jenkins is happy now.

I'll do some more testing at my office tomorrow to make sure it solves
our issue on my shared computer.

Jim
Reply all
Reply to author
Forward
0 new messages