blocks|key|1229583|text|我认为您不可能一步一步就做到这一点(实际上，我很惊讶Maven没有抱怨您的设置，也不知道应用了哪一种设置)，我建议您使用概要文件或者过滤来管理这个用例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229584|如果您的web.xml非常不同，您只需将maven-war插件配置放在两个配置文件中即可。或者，更好的是，你可以把它们合并成这样的东西：|offset|length|style|CODE|1229585|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-war-plugin</artifactId>
++<version>2.1-beta-1</version>
++<configuration>
++++<webXml>src/main/config/${env}/web.xml</webXml>
++++<warName>cas-test</warName>
++</configuration>
</plugin>|code-block|syntax|javascript|1229586|并在两个配置文件中设置env属性，以便在构建时获取正确的web.xml。|1229587|<profiles>
++<profile>
++++<id>uat</id>
++++<properties>
++++++<env>test</env>
++++</properties>
++</profile>
++<profile>
++++<id>prod</id>
++++<properties>
++++++<env>prod</env>
++++</properties>
++</profile>
</profiles>|1229588|如果您的web.xml是相似的(也就是说，如果它们中只有值不同)，您可以在两个配置文件中定义属性及其值，并使用筛选来应用它们。就像这样：|1229589|<profiles>
++<profile>
++++<id>env-uat</id>
++++<activation>
++++++<property>
++++++++<name>env</name>
++++++++<value>uat</value>
++++++</property>
++++</activation>
++++<properties>
++++++<key1>uat_value_key_1</key1>
++++++<keyN>uat_value_key_n</keyN>
++++</properties>
++</profile>
++<profile>
++++<id>env-prod</id>
++++<activation>
++++++<property>
++++++++<name>env</name>
++++++++<value>prod</value>
++++++</property>
++++</activation>++
++++<properties>
++++++<key1>prod_value_key_1</key1>
++++++<keyN>prod_value_key_n</keyN>
++++</properties>
++</profile>
</profiles>|1229590|然后，通过在命令行上传递env属性来激活一个配置文件或另一个配置文件，例如：|1229591|mvn+-Denv=uat+package|1229592|另一种选择是将值放入特定的筛选器中，并在构建时选择正确的过滤器(如这个职位中的)。|1229593|有很多选择，但正如我所说，我认为如果不运行两次构建，您就无法做到这一点。|1229594|关于概要文件/筛选的更多资源：|1229595|Maven+Book:第11章.构建概要文件|unordered-list-item|1229596|Maven+Book:第15.3章。资源过滤|1229597|构建概要文件简介|1229598|在测试阶段使用替代的Maven配置文件|1229599|谷歌上的maven轮廓滤波搜索|1229600|entityMap|0|LINK|mutability|MUTABLE|url|http://www.jetbrains.net/devnet/thread/279955|1|http://www.sonatype.com/books/maven-book/reference/profiles.html|2|http://www.sonatype.com/books/maven-book/reference/resource-filtering-sect-description.html|3|http://maven.apache.org/guides/introduction/introduction-to-profiles.html|4|https://stackoverflow.com/questions/866102/use-an-alternative-maven-profile-during-test-phase|5|http://www.google.com/search?q=maven%2Bprofile%2B%2Bfiltering^0|0|4|7|0|0|B|3|S|7|0|0|4|7|0|0|0|0|X|4|0|0|0|0|0|M|1|0|0|M|2|0|0|8|3|0|0|J|4|0|4|9|5|0^^$0|@$1|2|3|4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|21|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|22|8|@$D|23|E|24|F|G]|$D|25|E|26|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|27|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|28|8|@$D|29|E|2A|F|G]]|9|@]|A|$]]|$1|S|3|T|5|J|7|2B|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|2C|8|@]|9|@]|A|$]]|$1|W|3|X|5|J|7|2D|8|@]|9|@]|A|$K|L]]|$1|Y|3|Z|5|6|7|2E|8|@]|9|@$D|2F|E|2G|1|2H]]|A|$]]|$1|10|3|11|5|6|7|2I|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2J|8|@]|9|@]|A|$]]|$1|14|3|15|5|16|7|2K|8|@]|9|@$D|2L|E|2M|1|2N]]|A|$]]|$1|17|3|18|5|16|7|2O|8|@]|9|@$D|2P|E|2Q|1|2R]]|A|$]]|$1|19|3|1A|5|16|7|2S|8|@]|9|@$D|2T|E|2U|1|2V]]|A|$]]|$1|1B|3|1C|5|16|7|2W|8|@]|9|@$D|2X|E|2Y|1|2Z]]|A|$]]|$1|1D|3|1E|5|16|7|30|8|@]|9|@$D|31|E|32|1|33]]|A|$]]|$1|1F|3|-4|5|6|7|34|8|@]|9|@]|A|$]]]|1G|$1H|$5|1I|1J|1K|A|$1L|1M]]|1N|$5|1I|1J|1K|A|$1L|1O]]|1P|$5|1I|1J|1K|A|$1L|1Q]]|1R|$5|1I|1J|1K|A|$1L|1S]]|1T|$5|1I|1J|1K|A|$1L|1U]]|1V|$5|1I|1J|1K|A|$1L|1W]]]]

I don't think you can do this in one step (actually, I'm surprised that Maven doesn't complain about your setup and wonder which one is applied) and I'd suggest to use profiles and maybe filtering to manage this use case. 

If your <code>web.xml</code> are really different, you could just put your maven-war-plugin configuration in two profiles. Or, better, you could merge them into something like this:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-war-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.1-beta-1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;webXml&gt;src/main/config/${env}/web.xml&lt;/webXml&gt;
 &lt;warName&gt;cas-test&lt;/warName&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

And set the <code>env</code> property in two profiles to pick up the right <code>web.xml</code> at build time.

<pre><code>&lt;profiles&gt;
 &lt;profile&gt;
 &lt;id&gt;uat&lt;/id&gt;
 &lt;properties&gt;
 &lt;env&gt;test&lt;/env&gt;
 &lt;/properties&gt;
 &lt;/profile&gt;
 &lt;profile&gt;
 &lt;id&gt;prod&lt;/id&gt;
 &lt;properties&gt;
 &lt;env&gt;prod&lt;/env&gt;
 &lt;/properties&gt;
 &lt;/profile&gt;
&lt;/profiles&gt;
</code></pre>

If your <code>web.xml</code> are similar (i.e. if only values differ in them), you could define properties and their values in two profiles and use filtering to apply them. Something like this:

<pre><code>&lt;profiles&gt;
 &lt;profile&gt;
 &lt;id&gt;env-uat&lt;/id&gt;
 &lt;activation&gt;
 &lt;property&gt;
 &lt;name&gt;env&lt;/name&gt;
 &lt;value&gt;uat&lt;/value&gt;
 &lt;/property&gt;
 &lt;/activation&gt;
 &lt;properties&gt;
 &lt;key1&gt;uat_value_key_1&lt;/key1&gt;
 &lt;keyN&gt;uat_value_key_n&lt;/keyN&gt;
 &lt;/properties&gt;
 &lt;/profile&gt;
 &lt;profile&gt;
 &lt;id&gt;env-prod&lt;/id&gt;
 &lt;activation&gt;
 &lt;property&gt;
 &lt;name&gt;env&lt;/name&gt;
 &lt;value&gt;prod&lt;/value&gt;
 &lt;/property&gt;
 &lt;/activation&gt; 
 &lt;properties&gt;
 &lt;key1&gt;prod_value_key_1&lt;/key1&gt;
 &lt;keyN&gt;prod_value_key_n&lt;/keyN&gt;
 &lt;/properties&gt;
 &lt;/profile&gt;
&lt;/profiles&gt;
</code></pre>

Then activate one profile or the other by passing the env property on the command line, e.g.:

<pre><code>mvn -Denv=uat package
</code></pre>

Another option would be to put the values into specific filters and pick up the right one at build time (like in <a href="http://www.jetbrains.net/devnet/thread/279955" rel="nofollow noreferrer">this post</a>).

There are really many options but as I said, I don't think you can do this without runngin the build twice. 

More resources on profiles/filtering:

<ul>
<li><a href="http://www.sonatype.com/books/maven-book/reference/profiles.html" rel="nofollow noreferrer">Maven Book: Chapter 11. Build Profiles</a></li>
<li><a href="http://www.sonatype.com/books/maven-book/reference/resource-filtering-sect-description.html" rel="nofollow noreferrer">Maven Book: Chapter 15.3. Resource Filtering</a></li>
<li><a href="http://maven.apache.org/guides/introduction/introduction-to-profiles.html" rel="nofollow noreferrer">Introduction to Build Profiles</a></li>
<li><a href="https://stackoverflow.com/questions/866102/use-an-alternative-maven-profile-during-test-phase">Use an alternative Maven Profile during test phase</a></li>
<li><a href="http://www.google.com/search?q=maven+profile++filtering" rel="nofollow noreferrer">maven profile filtering</a> search on Google</li>
</ul>

blocks|key|2752140|text|我认为这只能通过编写自定义Maven插件或干扰构建生命周期和两次运行war组装过程来实现(这只是一个模糊的想法)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2752141|也许您可以创建两个概要文件并使用不同的配置文件(mvn+-P+prof1+package、mvn+-P+prof2+package)运行目标两次，但是要小心生成的工件名称，它们不应该被覆盖。或者您可以创建一个使用其他插件并组装这两个war文件的自定义插件。|offset|length|style|CODE|2752142|entityMap^0|0|O|K|19|K|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

I think this can only be achieved by writing a custom Maven plugin or interfering with the build lifecycle and running the war assembling process twice (this is just a faint idea).

Maybe you could create two profiles and run the goal twice with different profiles (<code>mvn -P prof1 package</code>, <code>mvn -P prof2 package</code>), but be careful with the generated artifact names, they shouldn't be overwritten. Or you might be able to create a custom plugin that uses other plugins and assembles the two war files.

blocks|key|1229691|text|我通常建议使用概要文件并运行两个专用的构建。但是，应该可以使用maven-程序集-插件创建任意数量的工件。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1229692|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/plugins/maven-assembly-plugin/^0|V|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'd generally suggest to use profiles and run two dedicated builds. However, it should be possible to create any number of artifacts using the <a href="http://maven.apache.org/plugins/maven-assembly-plugin/" rel="nofollow noreferrer">maven-assembly-plugin</a>.

blocks|key|2752213|text|虽然我不使用Maven，而是使用常春藤，但通常应该这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2752214|将自己的应用程序发布到私有存储库/类似的JAR中，其中包含依赖项/其他静态内容，然后使用上下文特定的配置构建应用程序的部署特定WAR的单独项目设置。现在，通过构建任何单独的部署项目，您将获得实际应用程序的最新版本及其特定于构建的配置。|2752215|我认为，由于这在常春藤中是微不足道的，Maven应该能够轻松地做到这一点。|2752216|entityMap|0|LINK|mutability|MUTABLE|url|http://ant.apache.org/ivy/^0|G|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

While I don't use Maven but <a href="http://ant.apache.org/ivy/" rel="nofollow noreferrer">Ivy</a> instead, here's how you should generally do this:

Have your own application published in to a private repository/similar as JAR with its dependencies/other static stuff and then individual project settings for building the application's deployment specific WARs with context specific configurations. Now by building any of the individual deployment projects you get the latest version of your actual application with its build specific configurations.

I would assume that since this is trivial in Ivy, Maven should be able to do it just as easily.

blocks|key|1143937|text|这种骇人听闻的攻击(它打破了Maven声明意图而不是行动的想法)，但对我有用:我不得不产生两场战争，它们共享相同的后端代码基础，但在MVC控制器包上却各不相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1143938|在用几个插件敲了我的脑袋后，我想“嘿，我会很容易地在蚂蚁中完成它”，这导致我在“包”阶段(我们已经准备好了所有的文件)使用<maven-antrun-plugin>来生成战争。就像这样：|offset|length|style|CODE|1143939|<plugin>
++<artifactId>maven-antrun-plugin</artifactId>
++++<version>1.3</version>
++++<executions>
++++++<execution>
++++++++<phase>package</phase>
++++++++<goals>
++++++++++<goal>run</goal>
++++++++</goals>
++++++++<configuration>
++++++++++<tasks>++
++++++++++++<delete+file="target/war-1.war"+/>
++++++++++++<delete+file="target/war-2.war"+/>++++++++++++
++++++++++++<war+destfile="target/war-1.war">
++++++++++++++<fileset+dir="target/original">
++++++++++++++++<exclude+name="**/WEB-INF/classes/package_of_war2/**"+/>
++++++++++++++</fileset>
++++++++++++</war>
++++++++++++<war+destfile="target/war-2.war">
++++++++++++++<fileset+dir="target/original">
++++++++++++++++<exclude+name="**/WEB-INF/classes/package_of_war1/**"+/>
++++++++++++++</fileset>
++++++++++++</war>
++++++++++++<delete+file="target/original.war"+/
++++++++++</tasks>
++++++++</configuration>
++++++</execution>
++++</executions>
++</plugin>|code-block|syntax|javascript|1143940|(公平地说，我没有删除原始文件，但您应该能够删除。)|1143941|在您的示例中，您可以在没有备用web.xml的情况下打包一个war，在原始web.xml上重命名/移动它，然后打包第二个war。|1143942|entityMap^0|0|1P|L|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Sort-of-ugly hack (it breaks Maven's idea of declaring intentions instead of actions), but worked for me: I had to generate two wars which shared the same back-end code base, but varied on the MVC controller packages.

After banging my head with several plugins, I thought "hey, I'd do it easily in ant", which lead me to use <code>&lt;maven-antrun-plugin&gt;</code> to generate the wars during the "package" phase (on which we arlready have all the files). Sort of like this:

<pre><code>&lt;plugin&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.3&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;tasks&gt; 
 &lt;delete file="target/war-1.war" /&gt;
 &lt;delete file="target/war-2.war" /&gt; 
 &lt;war destfile="target/war-1.war"&gt;
 &lt;fileset dir="target/original"&gt;
 &lt;exclude name="**/WEB-INF/classes/package_of_war2/**" /&gt;
 &lt;/fileset&gt;
 &lt;/war&gt;
 &lt;war destfile="target/war-2.war"&gt;
 &lt;fileset dir="target/original"&gt;
 &lt;exclude name="**/WEB-INF/classes/package_of_war1/**" /&gt;
 &lt;/fileset&gt;
 &lt;/war&gt;
 &lt;delete file="target/original.war" /
 &lt;/tasks&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

(to be fair, I did not delete the original file, but you should be able to do so.)

In your case, you could package one war without the alternate web.xml, rename/move it over the original web.xml, then package the second war.

blocks|key|1229805|text|您可以告诉Maven程序集插件只生成两个程序集。您只需为希望创建的每个输出编写一个程序集描述符文件，并在插件配置中列出它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229806|例如，我使用它生成一个WAR文件和一个TGZ文件，但是没有理由不能以相同的方式进行两次WAR。然后mvn包将生成这两个文件。|1229807|++++++++<plugin>
++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++<version>2.3</version>
++++++++++++<configuration>
++++++++++++++++<descriptors>
++++++++++++++++++++<descriptor>src/main/assembly/assembly-war.xml</descriptor>
++++++++++++++++++++<descriptor>src/main/assembly/assembly-dist.xml</descriptor>
++++++++++++++++</descriptors>
++++++++++++</configuration>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>dist-assembly</id>
++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>single</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>|code-block|syntax|javascript|1229808|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You can tell the Maven Assembly plugin to simply generate two assemblies. You just write an assembly descriptor file for each output you wish to create and list them in the plugin config. 

For example I'm using it to generate a WAR file and a TGZ file, but there's no reason you can't do two WARs in the same way. mvn package will then generate both files.

<pre><code> &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.3&lt;/version&gt;
 &lt;configuration&gt;
 &lt;descriptors&gt;
 &lt;descriptor&gt;src/main/assembly/assembly-war.xml&lt;/descriptor&gt;
 &lt;descriptor&gt;src/main/assembly/assembly-dist.xml&lt;/descriptor&gt;
 &lt;/descriptors&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;dist-assembly&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|1229851|text|老问题，但我想回答是否完整。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229852|您可以在一个构建步骤中很简单地使用带有两个执行的war插件来完成这个任务。参见下面的示例代码：|1229853|++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-war-plugin</artifactId>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>build-context-one</id>
++++++++++++++++++++<phase>install</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>war</goal>
++++++++++++++++++++</goals>
++++++++++++++++++++<configuration>
++++++++++++++++++++++++<classifier>context-one</classifier>
++++++++++++++++++++++++<webResources>
++++++++++++++++++++++++++++<resource>
++++++++++++++++++++++++++++++++<filtering>true</filtering>
++++++++++++++++++++++++++++++++<directory>src/main/webapp</directory>
++++++++++++++++++++++++++++++++<includes>
++++++++++++++++++++++++++++++++++++<include>**</include>
++++++++++++++++++++++++++++++++</includes>
++++++++++++++++++++++++++++</resource>
++++++++++++++++++++++++++++<resource>
++++++++++++++++++++++++++++++++<directory>your-context-one-directory</directory>
++++++++++++++++++++++++++++</resource>
++++++++++++++++++++++++</webResources>
++++++++++++++++++++</configuration>
++++++++++++++++</execution>
++++++++++++++++<execution>
++++++++++++++++++++<id>build-context-two</id>
++++++++++++++++++++<phase>install</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>war</goal>
++++++++++++++++++++</goals>
++++++++++++++++++++<configuration>
++++++++++++++++++++++++<classifier>classifier-two</classifier>
++++++++++++++++++++++++<webResources>
++++++++++++++++++++++++++++<resource>
++++++++++++++++++++++++++++++++<filtering>true</filtering>
++++++++++++++++++++++++++++++++<directory>src/main/webapp</directory>
++++++++++++++++++++++++++++++++<includes>
++++++++++++++++++++++++++++++++++++<include>**</include>
++++++++++++++++++++++++++++++++</includes>
++++++++++++++++++++++++++++</resource>
++++++++++++++++++++++++++++<resource>
++++++++++++++++++++++++++++++++<directory>your-context-two-directory</directory>
++++++++++++++++++++++++++++</resource>
++++++++++++++++++++++++</webResources>
++++++++++++++++++++</configuration>
++++++++++++++++</execution>
++++++++++++</executions>|code-block|syntax|javascript|1229854|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Old Question, but I want to answer for completeness.

You can do this in one build step very simply with the war plugin with two executions. See the sample code below:

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-war-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;build-context-one&lt;/id&gt;
 &lt;phase&gt;install&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;war&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;classifier&gt;context-one&lt;/classifier&gt;
 &lt;webResources&gt;
 &lt;resource&gt;
 &lt;filtering&gt;true&lt;/filtering&gt;
 &lt;directory&gt;src/main/webapp&lt;/directory&gt;
 &lt;includes&gt;
 &lt;include&gt;**&lt;/include&gt;
 &lt;/includes&gt;
 &lt;/resource&gt;
 &lt;resource&gt;
 &lt;directory&gt;your-context-one-directory&lt;/directory&gt;
 &lt;/resource&gt;
 &lt;/webResources&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;execution&gt;
 &lt;id&gt;build-context-two&lt;/id&gt;
 &lt;phase&gt;install&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;war&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;classifier&gt;classifier-two&lt;/classifier&gt;
 &lt;webResources&gt;
 &lt;resource&gt;
 &lt;filtering&gt;true&lt;/filtering&gt;
 &lt;directory&gt;src/main/webapp&lt;/directory&gt;
 &lt;includes&gt;
 &lt;include&gt;**&lt;/include&gt;
 &lt;/includes&gt;
 &lt;/resource&gt;
 &lt;resource&gt;
 &lt;directory&gt;your-context-two-directory&lt;/directory&gt;
 &lt;/resource&gt;
 &lt;/webResources&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
</code></pre>

blocks|key|2752361|text|更简单：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2752362|只需创建一个多模块项目。|2752363|每个模块都有WAR打包:)|2752364|从父母的pom和瞧！|2752365|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

More simple:
Just create a multi modules project.
Each module would have the WAR packaging :)
Build from parent pom and voila !

When doing a <code>mvn install</code> I want to end up with 2 WAR files in my target directory. One will contain the production <code>web.xml</code> and the other will contain the test/uat <code>web.xml</code>.

I've tried this:

<pre><code>&lt;build&gt;
 &lt;finalName&gt;cas-server&lt;/finalName&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-war-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.1-beta-1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;webXml&gt;src/main/config/prod/web.xml&lt;/webXml&gt;
 &lt;warName&gt;cas-prod&lt;/warName&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-war-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.1-beta-1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;webXml&gt;src/main/config/test/web.xml&lt;/webXml&gt;
 &lt;warName&gt;cas-test&lt;/warName&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

But I only end up with the test WAR.

How do I get Maven 2 to build 2 separate WAR files

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在执行mvn install时，我希望目标目录中有2个WAR文件。一个包含production web.xml，另一个包含测试/uat web.xml。我试过这个：<build> <finalName>cas-server</finalName> <plugins> <plugin> ...

问如何使Maven 2生成两个单独的WAR文件
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使Maven 2生成两个单独的WAR文件EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使Maven 2生成两个单独的WAR文件
EN