maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Showalter (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MNG-5970) Directory path set in mojo by Maven is lowercased, causing it to not match actual directory
Date Mon, 01 Feb 2016 23:45:39 GMT
Jim Showalter created MNG-5970:
----------------------------------

             Summary: Directory path set in mojo by Maven is lowercased, causing it to not
match actual directory
                 Key: MNG-5970
                 URL: https://issues.apache.org/jira/browse/MNG-5970
             Project: Maven
          Issue Type: Bug
          Components: Plugin API
    Affects Versions: 3.0.3
         Environment: Linux
            Reporter: Jim Showalter


We have a custom mojo. It has this field:

	/**
	 * Location of the directory containing the pom.
	 * @parameter default-value="project.basedir"
	 * @required
	 */
    private String baseDir;

Our unit test for the mojo works fine locally, but fails in Jenkins CI.

The reason it fails is that the value of baseDir set by the Maven framework is all lowercase,
but the directory path on the Jenkins server has some uppercase.

We are not touching the value of baseDir, just taking it and immediately trying File[] files
= new File(baseDir).listFiles(), which blows up because baseDir lowercase doesn't exist.

Why is Maven not passing the directory path in as-is, instead of all lowercase?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message