brett 2004/05/07 15:37:15
Modified: xdocs Tag: MAVEN-1_0-BRANCH faq.fml
Log:
added FAQ regarding :get/:set jelly tags, and the property inheritence changes
Revision Changes Path
No revision
No revision
1.5.4.3 +40 -1 maven/xdocs/faq.fml
Index: faq.fml
===================================================================
RCS file: /home/cvs/maven/xdocs/faq.fml,v
retrieving revision 1.5.4.2
retrieving revision 1.5.4.3
diff -u -r1.5.4.2 -r1.5.4.3
--- faq.fml 10 Mar 2004 11:14:03 -0000 1.5.4.2
+++ faq.fml 7 May 2004 22:37:15 -0000 1.5.4.3
@@ -247,6 +247,27 @@
</faq>
</part>
+
+ <part id="jelly">
+ <title>Jelly Usage</title>
+ <faq id="plugin-variables">
+ <question>How do I get or set plugin properties from Jelly?</question>
+ <answer>
+ <p>Plugin properties can be used with the following tags:
+ <a href="/reference/maven-jelly-tags/tags.html#maven:get">maven:get</a> and
+ <a href="/reference/maven-jelly-tags/tags.html#maven:set">maven:set</a>.
+ (These replace the deprecated versions of
<code>${pom.getPluginContext(...).get/setVariable()}</code>
+ and <code>maven:pluginVar</code>.)</p>
+ <p>Example:</p>
+ <source>
+<maven:get plugin="maven-war-plugin" property="maven.war.src" var="warSourceDir"
/>
+<echo>The WAR source directory is ${warSourceDir}<echo>
+...
+<maven:set plugin="maven-multiproject-plugin"
property="maven.multiproject.includes" value="subprojects/*/project.xml"/>
+ </source>
+ </answer>
+ </faq>
+ </part>
<part id="errors">
<title>Errors</title>
@@ -291,7 +312,25 @@
</part>
<part id="recent-changes">
- <title>Recent Changes</title>
+ <title>Recent Changes (Migrating from older versions of Maven)</title>
+
+ <faq id="property-inheritence">
+ <question>Why are strange property values appearing from other parts of my
project?</question>
+ <answer>
+ <p>Early in RC3, the bug that caused project.properties file inheritence to
fail was fixed. This means
+ that if you extend another project.xml file, you also inherit the
project.properties and build.properties
+ files from the same directory.</p>
+ <p>While this was a highly demanded fix, some builds may have come to
depend on it not working (including
+ the Maven build itself!). This is usually due to having a master build
project that also serves as a base
+ project extended by a set of subprojects, and wanting the properties to
apply to the master, but not to the
+ subprojects.</p>
+ <p>We recommend that you separate these concerns by having both a master
build project and a parent project
+ for extension (see the maven-plugins CVS tree for an example).</p>
+ <p>However, should you need to maintain your old structure, and you are
encountering these problems, you can
+ add the following property to stop parents from being inherited:</p>
+ <source>maven.property.inheritence=false</source>
+ </answer>
+ </faq>
<faq id="classloader-property">
<question>Why shouldn't I use the dependency classloader override
property?</question>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
