blocks|key|3135002|text|我的第一个倾向是创建一个配置文件，该配置文件在env属性未设置时处于活动状态，并以某种方式使其失败。也许你可以写一个Maven插件来测试这个属性，如果它不存在就会失败？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3135003|或者，您可以使用一个非常小的ant-build脚本来测试它。|3135004|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My first inclination would be to make a Profile that's active whenever the env property is unset, and have it fail somehow. Perhaps you could write a Maven Plugin that tests for that property and fails if it's not present?

Alternately, you could probably test for it with a very small ant-build script.

blocks|key|353711|text|要详细说明edbrannin的替代解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353712|<project>
++<modelVersion>4.0.0</modelVersion>
++<groupId>com.yourcompany</groupId>
++<artifactId>yourproject</artifactId>
++<version>1.0-SNAPSHOT</version>
++<build>
++++<plugins>
++++++<plugin>
++++++++<artifactId>maven-antrun-plugin</artifactId>
++++++++<executions>
++++++++++<execution>
++++++++++++<id>checkParam</id>
++++++++++++<phase>initialize</phase>
++++++++++++<goals><goal>run</goal></goals>
++++++++++++<configuration>
++++++++++++++<tasks>
++++++++++++++++<fail+message="'env'+property+must+be+set"+unless="env"/>
++++++++++++++</tasks>
++++++++++++</configuration>
++++++++++</execution>
++++++++</executions>
++++++</plugin>
++++</plugins>
++</build>
</project>|code-block|syntax|javascript|353713|将为您提供以下输出：|353714|[INFO]+------------------------------------------------------------------------
[ERROR]+BUILD+ERROR
[INFO]+------------------------------------------------------------------------
[INFO]+An+Ant+BuildException+has+occured:+'env'+property+must+be+set|353715|我用最直接的方式(我个人喜欢的方式)做到这一点。|353716|您甚至可以使用包含<or>和<equals>标记的嵌套<condition>来控制一组允许值(参见Ant手册：http://ant.apache.org/manual/Tasks/conditions.html)|offset|length|style|CODE|353717|entityMap|0|LINK|mutability|MUTABLE|url|http://ant.apache.org/manual/Tasks/conditions.html^0|0|0|0|0|0|9|4|E|8|R|B|1J|1E|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@$O|16|P|17|Q|R]|$O|18|P|19|Q|R]|$O|1A|P|1B|Q|R]]|9|@$O|1C|P|1D|1|1E]]|A|$]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

To elaborate on edbrannin's alternate solution:

<pre><code>&lt;project&gt;
 &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
 &lt;groupId&gt;com.yourcompany&lt;/groupId&gt;
 &lt;artifactId&gt;yourproject&lt;/artifactId&gt;
 &lt;version&gt;1.0-SNAPSHOT&lt;/version&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;checkParam&lt;/id&gt;
 &lt;phase&gt;initialize&lt;/phase&gt;
 &lt;goals&gt;&lt;goal&gt;run&lt;/goal&gt;&lt;/goals&gt;
 &lt;configuration&gt;
 &lt;tasks&gt;
 &lt;fail message="'env' property must be set" unless="env"/&gt;
 &lt;/tasks&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/build&gt;
&lt;/project&gt;
</code></pre>

will give you the following output:

<pre><code>[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An Ant BuildException has occured: 'env' property must be set
</code></pre>

IMHO the most straightforward way to do it (the one I'd go for personally).

You could even control a set of allowed values using a nested <code>&lt;condition&gt;</code> containing <code>&lt;or&gt;</code> and <code>&lt;equals&gt;</code> tags (see the Ant manual: <a href="http://ant.apache.org/manual/Tasks/conditions.html" rel="nofollow noreferrer">http://ant.apache.org/manual/Tasks/conditions.html</a>)

blocks|key|3348005|text|也许你可以使用这样的变通方法:在Maven中，如果某个属性没有设置，你可以激活一个配置文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3348006|<project>
...
++++<profiles>
++++++++<profile>
++++++++++++<id>failure_profile</id>
++++++++++++<activation>
++++++++++++++++<property>
++++++++++++++++++++<name>!env</name>
++++++++++++++++</property>
++++++++++++</activation>
++++++++</profile>
++++</profiles>
</project>|code-block|syntax|javascript|3348007|然后你应该强制这个配置文件总是失败，例如使用maven-enforcer-plugin：|3348008|<profile>
++++<id>failure_profile</id>
++++...
++++<build>
++++++++<plugins>
++++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-enforcer-plugin</artifactId>
++++++++++++<executions>
++++++++++++++<execution>
++++++++++++++++<id>enforce</id>
++++++++++++++++<goals>
++++++++++++++++++<goal>enforce</goal>
++++++++++++++++</goals>
++++++++++++++++<configuration>
++++++++++++++++++<rules>
++++++++++++++++++++<AlwaysFail/>
++++++++++++++++++</rules>
++++++++++++++++++<fail>true</fail>
++++++++++++++++</configuration>
++++++++++++++</execution>
++++++++++++</executions>
++++++++++</plugin>
++++++++</plugins>
++++++</build>
</profile>|3348009|如果你不提供-Denv构建将会失败：|3348010|[INFO]+[enforcer:enforce+{execution:+enforce}]
[WARNING]+Rule+0:+org.apache.maven.plugins.enforcer.AlwaysFail+failed+with+message:
Always+fails!
[INFO]+---------------------------------------------------------
[ERROR]+BUILD+ERROR|3348011|嗯，它比Ant冗长得多，但纯粹是Maven+:)|3348012|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Maybe you could use such a workaround: in Maven you can activate a profile if some property is not set:

<pre><code>&lt;project&gt;
...
 &lt;profiles&gt;
 &lt;profile&gt;
 &lt;id&gt;failure_profile&lt;/id&gt;
 &lt;activation&gt;
 &lt;property&gt;
 &lt;name&gt;!env&lt;/name&gt;
 &lt;/property&gt;
 &lt;/activation&gt;
 &lt;/profile&gt;
 &lt;/profiles&gt;
&lt;/project&gt;
</code></pre>

Then you shall force this profile always fail, e.g. using maven-enforcer-plugin: 

<pre><code>&lt;profile&gt;
 &lt;id&gt;failure_profile&lt;/id&gt;
 ...
 &lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-enforcer-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;enforce&lt;/id&gt;
 &lt;goals&gt;
 &lt;goal&gt;enforce&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;rules&gt;
 &lt;AlwaysFail/&gt;
 &lt;/rules&gt;
 &lt;fail&gt;true&lt;/fail&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/build&gt;
&lt;/profile&gt;
</code></pre>

If you don't provide -Denv build will then fail:

<pre><code>[INFO] [enforcer:enforce {execution: enforce}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.AlwaysFail failed with message:
Always fails!
[INFO] ---------------------------------------------------------
[ERROR] BUILD ERROR
</code></pre>

Well, it's much more verbose then Ant, but pure Maven :)

blocks|key|352493|text|每个人都很亲近，但在enforcer中有一条规则，专门检查属性，不需要ant或时髦的配置文件：http://maven.apache.org/enforcer/enforcer-rules/requireProperty.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|352494|该规则还可以检查属性的值。|352495|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/enforcer/enforcer-rules/requireProperty.html^0|1B|1W|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Everyone is close, but there's a rule in the enforcer to specifically check for a property, no ant or funky profiles required: <a href="http://maven.apache.org/enforcer/enforcer-rules/requireProperty.html" rel="noreferrer">http://maven.apache.org/enforcer/enforcer-rules/requireProperty.html</a>

The rule can also check the value of the property.

I'm setting up a maven build, and the destination server needs to be specified on the command line as a property (which is then used to select the appropriate profile), eg

<pre><code>mvn -Denv=test
</code></pre>

I'd like the build to fail if the property's not set - is that possible?

Yes, I'm a Maven newbie.

EDIT: I've seen <a href="http://docs.codehaus.org/display/MAVENUSER/Required+Declaration+of+Properties" rel="noreferrer">this link</a>, which seems to imply it's not possible, but am not sure how up to date it is.

Can I force Maven 2 to require a property to be specified on the command line?

服务器

我正在设置一个maven构建，并且需要在命令行上将目标服务器指定为一个属性(然后使用该属性来选择适当的配置文件)，例如mvn -Denv=test如果没有设置属性，我希望构建失败--这可能吗？是的，我是Maven的新手。编辑：我见过，这似乎暗示这是不可能的，但不确定它是不是最新的。

问我可以强制Maven2要求在命令行上指定属性吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以强制Maven2要求在命令行上指定属性吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以强制Maven2要求在命令行上指定属性吗？
EN