不要回避Antrun插件。仅仅因为有些人倾向于认为Ant和Maven是对立的，但事实并非如此。如果你需要执行一些不可避免的一次性定制，请使用copy任务:

<project>
  [...]
  <build>
    <plugins>
      [...]
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <phase>deploy</phase>
            <configuration>
              <target>

                <!--
                  Place any Ant task here. You can add anything
                  you can add between <target> and </target> in a
                  build.xml.
                -->

              </target>
            </configuration>
            <goals>
              <goal>run</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
  [...]
</project>

In answering this question, I'm focusing on the details of what you asked. How do I copy a file? The question and the variable name lead me to a larger questions like: "Is there a better way to deal with server provisioning?" Use Maven as a build system to generate deployable artifact, then perform these customizations either in separate modules or somewhere else entirely. If you shared a bit more of your build environment, there might be a better way - there are plugins to provision a number of servers. Could you attach an assembly that is unpacked in the server's root? What server are you using?

再说一次，我相信有更好的办法。

总结一下上面的一些不错的答案:Maven被设计用来构建模块并将结果复制到Maven存储库。任何将模块复制到部署/安装程序输入目录的操作都必须在Maven核心功能的上下文之外进行，例如使用Ant/Maven复制命令。

If someone wants total control over the path of the source and destination paths, then using maven-antrun-plugin's copy task is the best option. This approach will allow you to copy between any paths on the system, irrespective of the concerned paths being within the mvn project or not. I had a situation where I had to do some unusual stuff like copy generated source files from target directory back to the src directory for further processing. In my situation, this was the only option that worked without fuss. Sample code snippet from pom.xml:

<plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-antrun-plugin</artifactId>
        <version>1.8</version>
        <executions>
            <execution>
                <phase>process-resources</phase>
                <configuration>
                <tasks>
                    <copy file="${basedir}/target/myome/minifyJsSrcDir/myome.min.js" todir="${basedir}/src/main/webapp/app/minifyJsSrcDir"/>
                </tasks>
                </configuration>
                <goals>
                <goal>run</goal>
                </goals>
            </execution>
        </executions>
</plugin>

我只能假设你的${project.server. server。Config}属性是自定义的，并且在标准目录布局之外。

如果是，那么我将使用复制任务。

复制任意文件的一种通用方法是利用Maven Wagon传输抽象。它可以通过文件、HTTP、FTP、SCP或WebDAV等协议处理各种目的地。

有一些插件提供了通过使用Wagon复制文件的工具。最值得注意的是:

Out-of-the-box Maven Deploy Plugin There is the deploy-file goal. It it quite inflexible but can get the job done: mvn deploy:deploy-file -Dfile=/path/to/your/file.ext -DgroupId=foo -DartifactId=bar -Dversion=1.0 -Durl=<url> -DgeneratePom=false Significant disadvantage to using Maven Deploy Plugin is that it is designated to work with Maven repositories. It assumes particular structure and metadata. You can see that the file is placed under foo/bar/1.0/file-1.0.ext and checksum files are created. There is no way around this. Wagon Maven Plugin Use the upload-single goal: mvn org.codehaus.mojo:wagon-maven-plugin:upload-single -Dwagon.fromFile=/path/to/your/file.ext -Dwagon.url=<url> The use of Wagon Maven Plugin for copying is straightforward and seems to be the most versatile.

在上面的例子中，<url>可以是任何支持的协议。请参阅现有马车供应商的列表。例如

在本地复制文件:file:///copy/to 拷贝文件到SSH远程主机:scp://host:22/copy/to

上面的例子在命令行中传递插件参数。或者，可以直接在POM中配置插件。然后调用就像mvn deploy:deploy-file@configured-execution-id那样简单。或者它可以绑定到特定的构建阶段。

请注意，对于像SCP这样的协议，你需要在你的POM中定义一个扩展:

<build>
  [...]
  <extensions>
    <extension>
      <groupId>org.apache.maven.wagon</groupId>
      <artifactId>wagon-ssh</artifactId>
      <version>2.12</version>
    </extension>
  </extensions>

如果要复制到的目标需要身份验证，则可以通过服务器设置提供凭据。传递给插件的repositoryId/serverId必须与设置中定义的服务器相匹配。

好吧，maven不应该擅长执行细粒度的任务，它不是bash或ant之类的脚本语言，而是声明性语言——您说—我需要一场战争或一只耳朵，然后您就得到了它。然而，如果你需要自定义战争或耳朵应该看起来像内部，你有一个问题。它不像ant那样是程序性的，而是声明性的。 这在一开始有一些好处，但到最后可能会有很多坏处。

我猜最初的概念是有好的插件，“只是工作”，但现实是不同的，如果你做非标准的东西。

然而，如果你在poms上投入足够的精力和少量的自定义插件，你会得到一个更好的构建环境，比如ant(当然这取决于你的项目，但对于更大的项目来说越来越正确)。