Maven Surefire

When temp directory is missing or not writeable, error messages should state that plainly somewhere

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.4.3
  • Fix Version/s: 2.7
  • Component/s: Maven Surefire Plugin
  • Labels:
    None
  • Environment:
    Cygwin on Windows XP Pro, maven 2.2.1, apache-tika-0.4, JDK 1.6.0_16
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

My TEMP and TMP environment variables were pointing to a directory I forgot to recreate after rebuilding my machine.
When I invoked "mvn install" from the apache-tika-0.4 directory, I got the following BUILD ERROR:
Error creating properties files for forking; nested exception is java.io.IOException: The system cannot find the path specified

The Java stack trace that maven's -e switch dumped indicated that surefire was trying to create a temp file, but didn't say where.

If I had seen "$TEMP/<filename>" or "/home/jcadow/TEMP/<filename>" in an error message or stack trace, it would have saved me 2 days.

Attaching build.log, the output of "mvn -e install".

TO REPRODUCE:
Install maven 2.2.1, download apache-tika-0.4, rename your temp directory, invoke 'mvn -e install' from apache-tika-0.4 base directory.

Activity

Hide
Permalink
Kristian Rosenvold added a comment -

Fixed because 2.7 no longer writes to temp. The empty catch block on the initial IOException has also been removed, so the error message for non-writeable files should be better.

Show
Kristian Rosenvold added a comment - Fixed because 2.7 no longer writes to temp. The empty catch block on the initial IOException has also been removed, so the error message for non-writeable files should be better.

People

  • Assignee:
    Unassigned
    Reporter:
    Jeff Cadow
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: