maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergei Ivanov (JIRA)" <>
Subject [jira] (MCOMPILER-180) bad path element "": no such file or directory
Date Wed, 05 Sep 2012 12:36:21 GMT
Sergei Ivanov created MCOMPILER-180:

             Summary: bad path element "": no such file or directory
                 Key: MCOMPILER-180
             Project: Maven 2.x Compiler Plugin
          Issue Type: Bug
    Affects Versions: 2.5.1
         Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000)
Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "2.6.18-194.32.1.el5", arch: "i386", family: "unix"
            Reporter: Sergei Ivanov
            Priority: Minor

When we added -Xlint:all to javac configuration, the following warning started to appear in
the build logs:

{noformat}[WARNING] bad path element "": no such file or directory{noformat}

I ran the maven build with -X and looked at the command line for javac, and it appears that
the lists for -classpath and -sourcepath are terminated with a colon. It should be a trivial
change to not output a path separator after the last element in the path.

Our config options are (as in the effective POM):


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message