Metro has been contributed to Eclipse Foundation. This repository is for legacy review only. Please refer to the Eclipse EE4J Metro project for the very latest
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.
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
SEVERE: null
java.io.FileNotFoundException: /tmp/jm.txt (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:179)
at java.io.FileOutputStream.(FileOutputStream.java:131)
at org.jvnet.jax_ws_commons.jaxws.AbstractJaxwsMojo.createPathFile(AbstractJaxwsMojo.java:476)
at org.jvnet.jax_ws_commons.jaxws.AbstractJaxwsMojo.exec(AbstractJaxwsMojo.java:363)
at org.jvnet.jax_ws_commons.jaxws.WsImportMojo.processLocalWsdlFiles(WsImportMojo.java:307)
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.
(source: https://www.java.net/forum/topic/glassfish/metro-and-jaxb/jaxws-maven-plugin-221-seems-leave-file-tmpjmtxt)
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.
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 SEVERE: null java.io.FileNotFoundException: /tmp/jm.txt (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.(FileOutputStream.java:131) at org.jvnet.jax_ws_commons.jaxws.AbstractJaxwsMojo.createPathFile(AbstractJaxwsMojo.java:476) at org.jvnet.jax_ws_commons.jaxws.AbstractJaxwsMojo.exec(AbstractJaxwsMojo.java:363) at org.jvnet.jax_ws_commons.jaxws.WsImportMojo.processLocalWsdlFiles(WsImportMojo.java:307)
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.
Affected Versions
[2.2.1]