Maven seems to truncate SQL import / misinterpret parameters under Linux - mysql

Question

I have a mavenized build (maven3) which has a module to load a mySQL database dump. This works fine under Windows, but not under Linux.
Running maven with the -X switch, it generates the following output:
[DEBUG] Using mysql at /usr/bin/mysql
[DEBUG] Command to execute: mysql -uMYUSER --password=**** -hlocalhost --quick --max_allowed_packet=16M --default-character-set=utf8 -e "source /this/path/to/my/database/dump/is/longer/than/70/characters/the_dump.sql"
[ERROR] ERROR 1102 (42000): Incorrect database name '/this/path/to/my/database/dump/is/longer/than/70/characters/the_dump.'
If I run the debug output on the commandline directly, the the_dump.sql script works fine. My guess is that Maven is not recognizing the parameters correctly, and/or truncating them (note that the second parameter is truncated at 70 characters in the error message). I can't afford to have the build failing under Windows - due to certain commands in the database script, it can't run correctly by passing it into mysql with a "<" pipe.
Here is the relevant pom snippet:
<build>
<resources>
<resource>
<directory>META-INF</directory>
<targetPath>META-INF</targetPath>
</resource>
<resource>
<directory>${dumps.target.dir}</directory>
</resource>
</resources>
<plugins>
<plugin>
<groupId>my.maven.plugin</groupId>
<artifactId>db-dumps-maven-plugin</artifactId>
<configuration>
<databasesToDump>${db.schemas.to.dump}</databasesToDump>
<documentStoreFolder>${documentstore.location}</documentStoreFolder>
<outputDirectory>${project.build.directory}/../${dumps.target.dir}</outputDirectory>
</configuration>
<executions>
<execution>
<id>dump-database</id>
<phase>prepare-package</phase>
<goals>
<goal>dump-db</goal>
</goals>
<inherited>false</inherited>
</execution>
</executions>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>build</id>
<build>
<plugins>
<plugin>
<groupId>my.maven.plugin</groupId>
<artifactId>db-dumps-maven-plugin</artifactId>
<executions>
<execution>
<id>create-database</id>
<phase>initialize</phase>
<goals>
<goal>create-db</goal>
</goals>
<inherited>false</inherited>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
And the execute snippet from the db-dumps-maven-plugin:
#Override
public void execute() throws MojoExecutionException {
final Set<String> dumpsToInsertLowerCase = evaluateDumpsToInsert();
final List<File> sqlFiles = findFiles(folderWithDumps, ".sql", dumpsToInsertLowerCase);
getLog().info("Inserting dumps: " + sqlFiles);
for (final File sqlFile : sqlFiles) {
String createCommand = "mysql -u%s --password=%s -h%s --quick --max_allowed_packet=16M --default-character-set=utf8 -e \"source %s\"";
Object[] createArgs = {username, password, hostname, sqlFile.getAbsolutePath().replace("\\", "/")};
executeCommand(createCommand, createArgs);
}
}
public void executeCommand(final String command, final Object[] arguments) {
final String commandToExecute = String.format(command, arguments);
mavenPlugin.getLog().debug("Command to execute: " + commandToExecute);
try {
final Process child = Runtime.getRuntime().exec(commandToExecute);
final InputStream inputStream = child.getInputStream();
readAndCloseStream(inputStream, false);
final InputStream errorStream = child.getErrorStream();
readAndCloseStream(errorStream, true);
// prevent leaking file descriptors, close stream
try {
child.getOutputStream().close();
} catch (final IOException ioe) {
mavenPlugin.getLog().warn("Unable to close stream. " + ioe);
}
// check return value
// 0 means a normal program termination
final int exitValue = child.exitValue();
if (exitValue != 0) {
throw new RuntimeException("Executing command failed. Exit code: " + exitValue);
}
} catch (final IOException e) {
throw new RuntimeException(e);
}
}
Any idea why this happens, and how to make maven correctly interpret the source command?