[
https://jira.codehaus.org/browse/MCOMPILER-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311188#comment-311188
]
selckin commented on MCOMPILER-180:
-----------------------------------
This is probably because of "Class-Path" entries in the
manifest(META-INF/MANIFEST.MF ) of some dependency, and javac honors those
(wtf!) and adds them.
Disable the warning: -Xlint:-path
> bad path element "": no such file or directory
> ----------------------------------------------
>
> Key: MCOMPILER-180
> URL: https://jira.codehaus.org/browse/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):
> {code:lang=xml}
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.5.1</version>
> <inherited>true</inherited>
> <configuration>
> <fork>true</fork>
> <showDeprecation>true</showDeprecation>
> <showWarnings>true</showWarnings>
> <source>1.6</source>
> <target>1.6</target>
> <compilerVersion>1.6</compilerVersion>
> <compilerArgument>-Xlint:all</compilerArgument>
> <testCompilerArgument>-Xlint:all</testCompilerArgument>
> </configuration>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
