blocks|key|3090701|text|好的，我认为下面的代码可能会满足你的需求。这种方法的缺点是，在执行后续构建时，每次部署之间会有一段时间间隔。这可以接受吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3090702|在每个项目中定义一个具有相同名称的概要文件(比如"publish")。在该配置文件中，您可以定义一个配置，以使用antrun-plugin通过FTP传递文件(见下文)。|3090703|在父项目中，您将有一个modules元素，将每个项目定义为一个模块。如果您运行mvn+install+-P+publish，那么每个项目都将在启用发布概要文件的情况下依次构建，并在安装阶段将最终工件发布到目标。如果需要部署其他文件，请相应地修改include+element。|offset|length|style|CODE|3090704|注意:+FTP任务的参数已设置为属性，这允许从命令行覆盖它们和/或从父POM继承它们。|3090705|<profiles>
++<profile>
++++<id>publish</id>
++++<plugin>
++++++<groupId>org.apache.maven.plugins</groupId>
++++++<artifactId>maven-antrun-plugin</artifactId>
++++++<executions>
++++++++<execution>
++++++++++<id>ftp</id>
++++++++++<phase>install</phase>
++++++++++<configuration>
++++++++++++<tasks>
++++++++++++++<ftp+action="send"+
++++++++++++++++++server="${ftp.host}"+remotedir="${ftp.remotedir}"+
++++++++++++++++++userid="${ftp.userid}"+password="${ftp.password}"+
++++++++++++++++++depends="${ftp.depends}"+verbose="${ftp.verbose}">
++++++++++++++++<fileset+dir="${project.build.directory}">
++++++++++++++++++<include+
++++++++++++++++++++name="${project.build.finalName}.${project.packaging}"/>
++++++++++++++++</fileset>
++++++++++++++</ftp>
++++++++++++</tasks>
++++++++++</configuration>
++++++++++<goals>
++++++++++++<goal>run</goal>
++++++++++</goals>
++++++++</execution>
++++++</executions>
++++++<dependencies>
++++++++<dependency>
++++++++++<groupId>commons-net</groupId>
++++++++++<artifactId>commons-net</artifactId>
++++++++++<version>1.4.1</version>
++++++++</dependency>
++++++++<dependency>
++++++++++<groupId>ant</groupId>
++++++++++<artifactId>ant-commons-net</artifactId>
++++++++++<version>1.6.5</version>
++++++++</dependency>
++++++++<dependency>
++++++++++<groupId>ant</groupId>
++++++++++<artifactId>ant-nodeps</artifactId>
++++++++++<version>1.6.5</version>
++++++++</dependency>
++++++</dependencies>
++++</plugin>
++++<properties>
++++++<ftp.host>hostname</ftp.host>
++++++<ftp.remotedir>/opt/path/to/install</ftp.remotedir>
++++++<ftp.userid>user</ftp.userid>
++++++<ftp.password>mypassword</ftp.password>
++++++<ftp.depends>yes</ftp.depends>
++++++<ftp.verbose>no</ftp.verbose>++++++++++
++++</properties>
++</profile>
</profiles>|code-block|syntax|javascript|3090706|3090707|更新:基于您的评论:您可以使用依赖项插件下载每个依赖项，但父项不能对子项具有依赖项，它将在子项之前构建。这必须是另一个项目。您还需要在某个地方保存部署它们的位置的信息。目前，您在各个项目中都有目标信息，因此无法在部署程序项目中访问这些信息。|3090708|采用这种方法，您可以在新项目中定义多个概要文件，每个工件一个。每个概要文件都定义了一个依赖项:复制执行以获取jar，并为其中一个项目定义了antrun执行。可以从概要文件中提取公共配置(例如antrun插件的依赖项)。还要注意，如果您定义了多个概要文件，则属性将被合并，因此您可能需要使用工件名称来限定它们，例如ftp.artifact1.host。|3090709|<profiles>
++<profile>
++++<id>deploy-artifact1</id>
++++<plugin>
++++++<groupId>org.apache.maven.plugins</groupId>
++++++<artifactId>maven-dependency-plugin</artifactId>
++++++<executions>
++++++++<execution>
++++++++++<id>copy-dependency</id>
++++++++++<phase>prepare-package</phase>
++++++++++<goals>
++++++++++++<goal>copy</goal>
++++++++++</goals>
++++++++++<configuration>
++++++++++++<artifactItems>
++++++++++++++<artifactItem>
++++++++++++++++<groupId>name.seller.rich</groupId>
++++++++++++++++<artifactId>artifact1</artifactId>
++++++++++++++++<version>1.0.0</version>
++++++++++++++++<type>jar</type>
++++++++++++++++<overWrite>false</overWrite>
++++++++++++++</artifactItem>
++++++++++++</artifactItems>
++++++++++++<outputDirectory>${project.build.directory}/deploy-staging</outputDirectory>
++++++++++++<overWriteReleases>false</overWriteReleases>
++++++++++</configuration>
++++++++</execution>
++++++</executions>
++++</plugin>
++++<plugin>
++++++<groupId>org.apache.maven.plugins</groupId>
++++++<artifactId>maven-antrun-plugin</artifactId>
++++++<executions>
++++++++<execution>
++++++++++<id>ftp</id>
++++++++++<phase>install</phase>
++++++++++<configuration>
++++++++++++<tasks>
++++++++++++++<ftp+action="send"+
++++++++++++++++++server="${ftp.host}"+remotedir="${ftp.remotedir}"+
++++++++++++++++++userid="${ftp.userid}"+password="${ftp.password}"+
++++++++++++++++++depends="${ftp.depends}"+verbose="${ftp.verbose}">
++++++++++++++++<fileset+dir="${project.build.directory}+includes="deploy-staging/"/>
++++++++++++++</ftp>
++++++++++++</tasks>
++++++++++</configuration>
++++++++++<goals>
++++++++++++<goal>run</goal>
++++++++++</goals>
++++++++</execution>
++++++</executions>
++++</plugin>
++++<properties>
++++++
++++++<ftp.host>hostname</ftp.host>
++++++<ftp.remotedir>/opt/path/to/install</ftp.remotedir>
++++++<ftp.userid>user</ftp.userid>
++++++<ftp.password>mypassword</ftp.password>
++++++<ftp.depends>yes</ftp.depends>
++++++<ftp.verbose>no</ftp.verbose>++++++++++
++++</properties>
++</profile>
</profiles>++|3090710|entityMap^0|0|0|13|M|3M|7|0|0|0|0|0|4C|I|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@$F|12|G|13|H|I]|$F|14|G|15|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|17|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|19|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1A|8|@$F|1B|G|1C|H|I]]|9|@]|A|$]]|$1|V|3|W|5|N|7|1D|8|@]|9|@]|A|$O|P]]|$1|X|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|Y|$]]

Ok, I think the following might do what you need. The drawback of this approach is that there will be an interval between each deployment as the subsequent build is executed. Is this acceptable?

Define a profile in each project with the same name (say "publish"). Within that profile you can define a configuration to use the antrun-plugin to deliver the files with FTP (see below).

In the parent project you'll have a modules element, defining each project as a module. If you run <code>mvn install -P publish</code>, each project will be built in turn with the publish profile enabled, and the final artifact published to the target during the install phase. If you need to deploy additional files, modify the include <code>element</code> accordingly.

Note the parameters for the FTP task have been set as properties, this allows them to be overridden from the command-line and/or inherited from the parent POM.

<pre><code>&lt;profiles&gt;
 &lt;profile&gt;
 &lt;id&gt;publish&lt;/id&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;ftp&lt;/id&gt;
 &lt;phase&gt;install&lt;/phase&gt;
 &lt;configuration&gt;
 &lt;tasks&gt;
 &lt;ftp action="send" 
 server="${ftp.host}" remotedir="${ftp.remotedir}" 
 userid="${ftp.userid}" password="${ftp.password}" 
 depends="${ftp.depends}" verbose="${ftp.verbose}"&gt;
 &lt;fileset dir="${project.build.directory}"&gt;
 &lt;include 
 name="${project.build.finalName}.${project.packaging}"/&gt;
 &lt;/fileset&gt;
 &lt;/ftp&gt;
 &lt;/tasks&gt;
 &lt;/configuration&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;commons-net&lt;/groupId&gt;
 &lt;artifactId&gt;commons-net&lt;/artifactId&gt;
 &lt;version&gt;1.4.1&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;ant&lt;/groupId&gt;
 &lt;artifactId&gt;ant-commons-net&lt;/artifactId&gt;
 &lt;version&gt;1.6.5&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;ant&lt;/groupId&gt;
 &lt;artifactId&gt;ant-nodeps&lt;/artifactId&gt;
 &lt;version&gt;1.6.5&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
 &lt;/plugin&gt;
 &lt;properties&gt;
 &lt;ftp.host&gt;hostname&lt;/ftp.host&gt;
 &lt;ftp.remotedir&gt;/opt/path/to/install&lt;/ftp.remotedir&gt;
 &lt;ftp.userid&gt;user&lt;/ftp.userid&gt;
 &lt;ftp.password&gt;mypassword&lt;/ftp.password&gt;
 &lt;ftp.depends&gt;yes&lt;/ftp.depends&gt;
 &lt;ftp.verbose&gt;no&lt;/ftp.verbose&gt; 
 &lt;/properties&gt;
 &lt;/profile&gt;
&lt;/profiles&gt;
</code></pre>

<hr>

Update: based on your comment: You could use the dependency plugin to download each dependency, except that a parent can't have a dependency on a child, and it will be built before the child. It would have to be another project. you also need to have somewhere the information for where to deploy them to. At the moment you have the target information in the individual projects so it isn't accessible in the deployer project.

Taking this approach, you can define multiple profiles in the new project, one for each artifact. Each profile defines a dependency:copy execution to obtain the jar and an antrun execution for one of the projects. Common configuration (such as the dependencies for the antrun plugin) can be pulled out of the profiles. Also be aware that the properties will be merged if you define multiple profiles, so yo may need to qualify them with the artifact name, for example <code>ftp.artifact1.host</code>.

<pre><code>&lt;profiles&gt;
 &lt;profile&gt;
 &lt;id&gt;deploy-artifact1&lt;/id&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;copy-dependency&lt;/id&gt;
 &lt;phase&gt;prepare-package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;copy&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;artifactItems&gt;
 &lt;artifactItem&gt;
 &lt;groupId&gt;name.seller.rich&lt;/groupId&gt;
 &lt;artifactId&gt;artifact1&lt;/artifactId&gt;
 &lt;version&gt;1.0.0&lt;/version&gt;
 &lt;type&gt;jar&lt;/type&gt;
 &lt;overWrite&gt;false&lt;/overWrite&gt;
 &lt;/artifactItem&gt;
 &lt;/artifactItems&gt;
 &lt;outputDirectory&gt;${project.build.directory}/deploy-staging&lt;/outputDirectory&gt;
 &lt;overWriteReleases&gt;false&lt;/overWriteReleases&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;ftp&lt;/id&gt;
 &lt;phase&gt;install&lt;/phase&gt;
 &lt;configuration&gt;
 &lt;tasks&gt;
 &lt;ftp action="send" 
 server="${ftp.host}" remotedir="${ftp.remotedir}" 
 userid="${ftp.userid}" password="${ftp.password}" 
 depends="${ftp.depends}" verbose="${ftp.verbose}"&gt;
 &lt;fileset dir="${project.build.directory} includes="deploy-staging/"/&gt;
 &lt;/ftp&gt;
 &lt;/tasks&gt;
 &lt;/configuration&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;properties&gt;
 &lt;!--if the properties differ between targets, qualify them with the artifact name--&gt;
 &lt;ftp.host&gt;hostname&lt;/ftp.host&gt;
 &lt;ftp.remotedir&gt;/opt/path/to/install&lt;/ftp.remotedir&gt;
 &lt;ftp.userid&gt;user&lt;/ftp.userid&gt;
 &lt;ftp.password&gt;mypassword&lt;/ftp.password&gt;
 &lt;ftp.depends&gt;yes&lt;/ftp.depends&gt;
 &lt;ftp.verbose&gt;no&lt;/ftp.verbose&gt; 
 &lt;/properties&gt;
 &lt;/profile&gt;
&lt;/profiles&gt; 
</code></pre>

blocks|key|330543|text|我会考虑使用maven-assembly-plugin来做这件事。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|330544|类似这样的东西可以用来从子项目中抓取文件，并将它们填充到输出目录中。|330545|<assembly>
++<id>xyzzy</id>
++<formats>
+++<format>zip</format>
++</formats>
++<fileSets>
+++<fileSet>
++++++<directory>../subproject1/target/</directory>
++++++<outputDirectory>/foo</outputDirectory>
++++++<includes>
++++++++<include>*.jar</include>
++++++</includes>
+++</fileSet>
+++<fileSet>
++++++<directory>../subproject1/target/html-output/</directory>
++++++<outputDirectory>/foo</outputDirectory>
++++++<includes>
++++++++<include>*.html</include>
++++++++<include>*.js</include>
++++++++<include>*.css</include>
++++++</includes>
++++</fileSet>+++++
++++<fileSet>
++++++<directory>../subproject2/target/</directory>
++++++<outputDirectory>/bar</outputDirectory>
++++++<includes>
++++++++<include>**/**</include>
++++++</includes>
++++++<excludes>
++++++++<exclude>**/*.exclude-this</exclude>
++++++</excludes>
++++</fileSet>
++</fileSets>+
</assembly>|code-block|syntax|javascript|330546|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/plugins/maven-assembly-plugin/^0|6|L|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

I would look at using the <a href="http://maven.apache.org/plugins/maven-assembly-plugin/" rel="nofollow noreferrer">maven-assembly-plugin</a> to do this. 

Something like this can be used to grab the files from the child projects and stuff them in output directories. 

<pre><code>&lt;assembly&gt;
 &lt;id&gt;xyzzy&lt;/id&gt;
 &lt;formats&gt;
 &lt;format&gt;zip&lt;/format&gt;
 &lt;/formats&gt;
 &lt;fileSets&gt;
 &lt;fileSet&gt;
 &lt;directory&gt;../subproject1/target/&lt;/directory&gt;
 &lt;outputDirectory&gt;/foo&lt;/outputDirectory&gt;
 &lt;includes&gt;
 &lt;include&gt;*.jar&lt;/include&gt;
 &lt;/includes&gt;
 &lt;/fileSet&gt;
 &lt;fileSet&gt;
 &lt;directory&gt;../subproject1/target/html-output/&lt;/directory&gt;
 &lt;outputDirectory&gt;/foo&lt;/outputDirectory&gt;
 &lt;includes&gt;
 &lt;include&gt;*.html&lt;/include&gt;
 &lt;include&gt;*.js&lt;/include&gt;
 &lt;include&gt;*.css&lt;/include&gt;
 &lt;/includes&gt;
 &lt;/fileSet&gt; 
 &lt;fileSet&gt;
 &lt;directory&gt;../subproject2/target/&lt;/directory&gt;
 &lt;outputDirectory&gt;/bar&lt;/outputDirectory&gt;
 &lt;includes&gt;
 &lt;include&gt;**/**&lt;/include&gt;
 &lt;/includes&gt;
 &lt;excludes&gt;
 &lt;exclude&gt;**/*.exclude-this&lt;/exclude&gt;
 &lt;/excludes&gt;
 &lt;/fileSet&gt;
 &lt;/fileSets&gt; 
&lt;/assembly&gt;
</code></pre>

blocks|key|3090784|text|Maven实际上并不是为将jars部署到远程位置而设计的；它的主要用途是编译和打包工件。程序集和依赖项目标主要用于收集要打包到工件中的依赖项和文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3090785|话虽如此，maven确实有一个部署目标，该目标使用了一个名为旅行车的组件。这主要是为了部署到maven存储库。有一个名为Cargo的插件，可用于将工件部署到远程服务器，但它本身不会分解jar内容(它依赖于目标应用服务器来完成所有这些工作)。您也许能够自己扩展Maven旅行车的功能。|3090786|此外，还可以打包一个自定义的生命周期，但这已经进入了一些相当低级的maven+mojo+(双关语)。|3090787|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Maven is not really designed to deploy jars to a remote location; its main use is compiling and packaging artifacts. The assembly and dependency targets are primarily used to gather dependencies and files to package into an artifact.

Having said that, maven does have a deploy goal which uses a component called wagon. This is primarily intended to deploy to a maven repository. There is a plugin called Cargo that can be used to deploy artifacts to a remote server, but that doesn't explode the jar contents by itself (it relies on the target app server to do all that). You might be able to extend the Maven Wagon functionality yourself.

Also, it is possible to package a custom lifecycle, but that is getting into some pretty low level maven mojo (pun intended).

blocks|key|3090809|text|如果没有口令，则无法工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3090810|++++<profile>
++++++++<id>publish</id>
++++++++<build>
++++++++++++<plugins>
++++++++++++++++<plugin>
++++++++++++++++++++<artifactId>maven-antrun-plugin</artifactId>
++++++++++++++++++++<executions>
++++++++++++++++++++++++<execution>
++++++++++++++++++++++++++++<id>scp</id>
++++++++++++++++++++++++++++<phase>deploy</phase>
++++++++++++++++++++++++++++<configuration>
++++++++++++++++++++++++++++++++<tasks>
++++++++++++++++++++++++++++++++++++<scp+todir="user@host:some/remote/dir"
+++++++++++++++++++++++++++++++++++++++++sftp="true"
+++++++++++++++++++++++++++++++++++++++++keyfile="${user.home}/.ssh/devel-deploy.id_dsa"
+++++++++++++++++++++++++++++++++++++++++failonerror="false"
+++++++++++++++++++++++++++++++++++++++++verbose="true"
+++++++++++++++++++++++++++++++++++++++++passphrase="nopass"
++++++++++++++++++++++++++++++++++++>
++++++++++++++++++++++++++++++++++++++++<fileset+dir="${project.build.directory}">
++++++++++++++++++++++++++++++++++++++++++++<include
++++++++++++++++++++++++++++++++++++++++++++++++name="${project.build.finalName}.${project.packaging}"/>
++++++++++++++++++++++++++++++++++++++++</fileset>
++++++++++++++++++++++++++++++++++++</scp>
++++++++++++++++++++++++++++++++</tasks>
++++++++++++++++++++++++++++</configuration>
++++++++++++++++++++++++++++<goals>
++++++++++++++++++++++++++++++++<goal>run</goal>
++++++++++++++++++++++++++++</goals>
++++++++++++++++++++++++</execution>
++++++++++++++++++++</executions>
++++++++++++++++++++<dependencies>
++++++++++++++++++++++++<dependency>
++++++++++++++++++++++++++++<groupId>org.apache.ant</groupId>
++++++++++++++++++++++++++++<artifactId>ant-jsch</artifactId>
++++++++++++++++++++++++++++<version>1.9.4</version>
++++++++++++++++++++++++</dependency>
++++++++++++++++++++</dependencies>
++++++++++++++++</plugin>
++++++++++++</plugins>
++++++++</build>
++++</profile>|code-block|syntax|javascript|3090811|然而，我最喜欢的是|3090812|++++<profile>
++++++++<id>upload-devel</id>
++++++++<build>
++++++++++++<plugins>
++++++++++++++++<plugin>
++++++++++++++++++++<artifactId>maven-antrun-plugin</artifactId>
++++++++++++++++++++<executions>
++++++++++++++++++++++++<execution>
++++++++++++++++++++++++++++<id>upload-devel</id>
++++++++++++++++++++++++++++<phase>deploy</phase>
++++++++++++++++++++++++++++<configuration>
++++++++++++++++++++++++++++++++<target>
++++++++++++++++++++++++++++++++++++<exec+executable="rsync"+failonerror="false">
++++++++++++++++++++++++++++++++++++++++<arg+value="-aiz"+/>
++++++++++++++++++++++++++++++++++++++++<arg+value="${project.build.directory}/${project.artifactId}.${project.packaging}"+/>
++++++++++++++++++++++++++++++++++++++++<arg+value="user@host:some/remote/dir/."+/>
++++++++++++++++++++++++++++++++++++</exec>
++++++++++++++++++++++++++++++++</target>
++++++++++++++++++++++++++++</configuration>
++++++++++++++++++++++++++++<goals>
++++++++++++++++++++++++++++++++<goal>run</goal>
++++++++++++++++++++++++++++</goals>
++++++++++++++++++++++++</execution>
++++++++++++++++++++</executions>
++++++++++++++++</plugin>
++++++++++++</plugins>
++++++++</build>
++++</profile>|3090813|虽然我不知道它在不同平台上的兼容性如何。|3090814|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Does not work without passphrase.

<pre><code> &lt;profile&gt;
 &lt;id&gt;publish&lt;/id&gt;
 &lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;scp&lt;/id&gt;
 &lt;phase&gt;deploy&lt;/phase&gt;
 &lt;configuration&gt;
 &lt;tasks&gt;
 &lt;scp todir="user@host:some/remote/dir"
 sftp="true"
 keyfile="${user.home}/.ssh/devel-deploy.id_dsa"
 failonerror="false"
 verbose="true"
 passphrase="nopass"
 &gt;
 &lt;fileset dir="${project.build.directory}"&gt;
 &lt;include
 name="${project.build.finalName}.${project.packaging}"/&gt;
 &lt;/fileset&gt;
 &lt;/scp&gt;
 &lt;/tasks&gt;
 &lt;/configuration&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.apache.ant&lt;/groupId&gt;
 &lt;artifactId&gt;ant-jsch&lt;/artifactId&gt;
 &lt;version&gt;1.9.4&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/build&gt;
 &lt;/profile&gt;
</code></pre>

However, my favourite is

<pre><code> &lt;profile&gt;
 &lt;id&gt;upload-devel&lt;/id&gt;
 &lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;upload-devel&lt;/id&gt;
 &lt;phase&gt;deploy&lt;/phase&gt;
 &lt;configuration&gt;
 &lt;target&gt;
 &lt;exec executable="rsync" failonerror="false"&gt;
 &lt;arg value="-aiz" /&gt;
 &lt;arg value="${project.build.directory}/${project.artifactId}.${project.packaging}" /&gt;
 &lt;arg value="user@host:some/remote/dir/." /&gt;
 &lt;/exec&gt;
 &lt;/target&gt;
 &lt;/configuration&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/build&gt;
 &lt;/profile&gt;
</code></pre>

though I don't know how compatible that is over different platforms.

blocks|key|3303655|text|下面的POM将有助于将jar文件从项目构建目录复制到远程SFTP/FTP服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3303656|3303657|使用命令mvn+install+-Dftp.password=password|ordered-list-item|offset|length|style|BOLD|3303658|3303659|由于出于安全原因，我想从命令提示符传递密码，所以在执行上述命令后，我使用了-Dftp.password=password，所有来自maven项目目标文件夹的jar文件都将部署到server.com上的MAVEN文件夹中|3303660|++++<plugin>++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++<artifactId>maven-antrun-plugin</artifactId>

++++<executions>
++++++++<execution>
++++++++++++<id>ftp</id>
++++++++++++<phase>install</phase>
++++++++++++<configuration>
++++++++++++++++<tasks>
++++++++++++++++++++<scp+todir="user@server.com:/MAVEN/"
++++++++++++++++++++++++sftp="true"+port="22"+trust="true"+password="${ftp.password}"
++++++++++++++++++++++++failonerror="false"+verbose="true"+passphrase="">
++++++++++++++++++++++++<fileset+dir="${project.build.directory}">
++++++++++++++++++++++++++++<include+name="*.jar"+/>
++++++++++++++++++++++++</fileset>
++++++++++++++++++++</scp>
++++++++++++++++</tasks>
++++++++++++</configuration>
++++++++++++<goals>
++++++++++++++++<goal>run</goal>
++++++++++++</goals>
++++++++</execution>
++++</executions>
++++<dependencies>
++++++++<dependency>
++++++++++++<groupId>org.apache.ant</groupId>
++++++++++++<artifactId>ant-jsch</artifactId>
++++++++++++<version>1.9.4</version>
++++++++</dependency>
++++</dependencies>

</plugin>|code-block|syntax|javascript|3303661|entityMap^0|0|0|4|Z|0|0|11|N|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Z|8|@$F|10|G|11|H|I]]|9|@]|A|$]]|$1|M|3|N|5|O|7|12|8|@]|9|@]|A|$P|Q]]|$1|R|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|S|$]]

Below POM will help to copy jar's file from project build directory to remote SFTP/FTP server.

<ol>
<li>Use command mvn install -Dftp.password=password</li>
</ol>

Since I want to pass password from command prompt for security reason, I have used -Dftp.password=password
After execution of above command all the jar files from maven project target folder will be deployed in MAVEN folder on server.com

<pre><code> &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;

 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;ftp&lt;/id&gt;
 &lt;phase&gt;install&lt;/phase&gt;
 &lt;configuration&gt;
 &lt;tasks&gt;
 &lt;scp todir="user@server.com:/MAVEN/"
 sftp="true" port="22" trust="true" password="${ftp.password}"
 failonerror="false" verbose="true" passphrase=""&gt;
 &lt;fileset dir="${project.build.directory}"&gt;
 &lt;include name="*.jar" /&gt;
 &lt;/fileset&gt;
 &lt;/scp&gt;
 &lt;/tasks&gt;
 &lt;/configuration&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.apache.ant&lt;/groupId&gt;
 &lt;artifactId&gt;ant-jsch&lt;/artifactId&gt;
 &lt;version&gt;1.9.4&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;

&lt;/plugin&gt;
</code></pre>

I have this task for the project with 4 nested subprojects using Maven:

<ol>
<li>For each child: jar-up resource directory including project dependencies</li>
<li>Move up to the parent project</li>
<li>With a single command extract all created archives into various remote destinations (full install), that may include http server, app server, file server, etc. (mostly *NIX). Destination is provided on subproject level</li>
<li>It should also be possible to unzip/copy from the individual subproject (partial install)</li>
</ol>

Files are not Java - mostly various scripts and HTML

I'm looking at the various plugins to help with the task: assembly, dependency, antrun, unzip. Dependency looks promising but I need to unzip not only dependency jars but the (sub)project content as well. Also since I can't really tight the operation to the Maven lifecycle how would I trigger remote install? mvn dependency:unpack? That's not very descriptive or intuitive. Is is possible to create a custom goal (e.g. project:install) without writing a plugin?

Using Maven is company standard so please do not offer alternatives - I'm pretty much stuck with what I have

Using Maven for deployment

服务器

Java

我使用Maven对包含4个嵌套子项目的项目执行以下任务：jar-up资源目录包括项目dependenciesMove到父项目只需一个命令就可以解压所有创建的归档文件到各种远程目标(完全安装)，其中可能包括http服务器、应用服务器、文件服务器等(主要是*NIX)。目标位置在子项目级上提供，也可以从单个子项目(部分安装)...

问使用Maven进行部署
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Maven进行部署EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Maven进行部署
EN