jaxws-maven-plugin 2.2.1 seems to leave a file /tmp/jm.txt
Release 2.2.1 of the jaxws-maven-plugin seems to create a file /tmp/jm.txt on each run without removing it afterwards.
This causes problems if multiple users on the same machine calls this plugin.
In AbstractJaxwsMojo.java the file refernence new File(System.getProperty("java.io.tmpdir", "jm.txt") is created in the method createPathFile. The methods first tries to remove the file, but if this fails, the fact is logged, but the method continues.
I do not see anything that tries to remove the file after its use in the exec() method.
If the wsimport goal of jaxws-maven-plugin is run with one WSDL by user 'a' and then afterwards by another user 'b' for another WSDL, the file for the first user is still used, typically causing something like
[WARNING] cannot remove obsolete classpath setting file: /tmp/jm.txt
28-May-2013 10:08:57 org.jvnet.jax_ws_commons.jaxws.AbstractJaxwsMojo createPathFile
java.io.FileNotFoundException: /tmp/jm.txt (Permission denied)
at java.io.FileOutputStream.open(Native Method)
Depending on the actual contents of old contents of jm.txt now being used by the plugin, this may or may not cause compilation problems later.
Other errors may happen if several invocations of the plugin are run simultaneously, even if run by the same user.
I see two problems here:
1. using a fixed filename for several invocations may cause them to mix up.
2. the file should be deleted when no longer needed.
For now, I'm reverting to release 2.2.