← Back to branch summary

~ubuntu-branches/ubuntu/saucy/maven-enforcer/saucy

« back to all changes in this revision

Viewing changes to maven-enforcer-plugin/src/site/fml/faq.fml

  • Committer: Package Import Robot
  • Author(s): Torsten Werner
  • Date: 2011-09-12 22:30:16 UTC
  • mfrom: (1.1.1 upstream)
  • Revision ID: package-import@ubuntu.com-20110912223016-e2pk04avoq8bur7t
Tags: 1.0-1
* Team upload
* New upstream release.
* Add more Build-Depends.

Show diffs side-by-side

added added

removed removed

Lines of Context:
maven-enforcer-plugin/src/site/fml/faq.fml
19
19
under the License.
20
20
-->
21
21
 
22
 
<faqs id="FAQ" title="Frequently Asked Questions">
 
22
<faqs xmlns="http://maven.apache.org/FML/1.0.1"
 
23
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 
24
  xsi:schemaLocation="http://maven.apache.org/FML/1.0.1 http://maven.apache.org/xsd/fml-1.0.1.xsd"
 
25
  id="FAQ" title="Frequently Asked Questions">
23
26
  <part id="General">
24
27
    <faq id="question">
25
28
      <question>Why can't I just use the prerequisites tag in the pom?</question>
27
30
        <p>
28
31
          The prerequisites tag was designed to be used by tools like plugins. It will work for regular projects, but it isn't
29
32
          inherited to their children. If it is set in a parent reactor, then Maven will do the check. However if one of the
30
 
          children are built, the check is not performed. The enforcer plugin is designed to allow centralized control over the build environment from 
 
33
          children are built, the check is not performed. The enforcer plugin is designed to allow centralized control over the build environment from
31
34
          a single "super-pom", and to allow greater flexibility in version specification by supporting ranges.
32
35
        </p>
33
36
      </answer>