brett 2004/03/10 03:14:03
Modified: xdocs Tag: MAVEN-1_0-BRANCH faq.fml
xdocs/reference Tag: MAVEN-1_0-BRANCH user-guide.xml
Log:
update doco for RC2
Revision Changes Path
No revision
No revision
1.5.4.2 +51 -48 maven/xdocs/faq.fml
Index: faq.fml
===================================================================
RCS file: /home/cvs/maven/xdocs/faq.fml,v
retrieving revision 1.5.4.1
retrieving revision 1.5.4.2
diff -u -r1.5.4.1 -r1.5.4.2
--- faq.fml 4 Mar 2004 17:45:56 -0000 1.5.4.1
+++ faq.fml 10 Mar 2004 11:14:03 -0000 1.5.4.2
@@ -111,17 +111,17 @@
</p>
<p>
This is typically caused by the cvs command not running correctly.
- The first port of call is to check maven.log, search the file for "SCM"
+ The first port of call is to check maven's output, search the lines
containing for "SCM"
</p>
<p>
<source>
<![CDATA[
-2003-02-26 06:42:04,975 INFO org.apache.maven.changelog.AbstractChangeLogGenerator
- SCM Working Directory: D:\Data\workspace\maven
-2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator
- SCM Command Line[0]: cvs
-2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator
- SCM Command Line[1]: -d
-2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator
- SCM Command Line[2]: :pserver:[EMAIL PROTECTED]:/home/cvsroot
-2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator
- SCM Command Line[3]: log
-2003-02-26 06:42:04,985 INFO org.apache.maven.changelog.AbstractChangeLogGenerator
- SCM Command Line[4]: -d 2003-01-27
+SCM Working Directory: D:\Data\workspace\maven
+SCM Command Line[0]: cvs
+SCM Command Line[1]: -d
+SCM Command Line[2]: :pserver:[EMAIL PROTECTED]:/home/cvsroot
+SCM Command Line[3]: log
+SCM Command Line[4]: -d 2003-01-27
]]>
</source>
</p>
@@ -143,15 +143,7 @@
<faq id="speeding-maven">
<question>Maven takes a long time to load. Is there anyway to speed things
?</question>
<answer>
- There are several things that you can do to accelerate this. First,
- you should delete the plugins that you don't use. Some plugins are
- platform-specific, so you can safely delete those that are not
- intended to run on your platform.
- <b>
- Some plugins depend on other plugins. Please delete plugins with care.
- </b>
- Once you are sure that you have all the plugins that you need, you
- can use the
+ You can use the
<a href="reference/plugins/console/index.html">Console Plugin</a> to
get an interactive shell that will let load Maven once and run as many
goals as you want. On average machines it takes something like
@@ -193,32 +185,6 @@
</answer>
</faq>
- <faq id="BrokenManifestInBeta9">
- <question>My jars don't work under my application server</question>
- <answer>
- <p>There is a bug in Maven Beta 9 that causes jars to be produced with
invalid manifests.
- The problem with the manifests only comes to light when using the jars
inside an Extension-aware
- program - eg. Tomcat.
- </p>
- <p>
- <strong>If you are running beta-10 or later, you do not need to do
this</strong>
- </p>
- <p>
- <a
href="http://projects.walding.com/maven-patches/maven-jar-plugin-1.0.jar";>
- http://projects.walding.com/maven-patches/maven-jar-plugin-1.0.jar
- </a> resolves this issue and is built from CVS between beta 9 and 10.
- </p>
- <p>
- Installation
- </p>
- <source>
-rm -r $MAVEN_HOME/plugins/maven-jar-plugin-1.0
-rm $MAVEN_HOME/plugins/maven-jar-plugin-1.0.jar
-wget -P $MAVEN_HOME/plugins
http://projects.walding.com/maven-patches/maven-jar-plugin-1.0.jar
- </source>
- </answer>
- </faq>
-
<faq id="BadXSLT">
<question>How do I get the XSLT tasks to work?</question>
<answer>
@@ -302,7 +268,7 @@
This problem has been observed when a version of Jelly used as a
dependency is different than the one distributed with Maven.
<a
href="http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-20030211.141339.jar";>This</a>
- is the version of Jelly that is distributed with Maven 1.0-beta-8.
+ is the version of Jelly that is distributed with Maven 1.0-rc2.
If you align your versions of Jelly you should be able to generate
your site. We hope to alleviate these problems with real ClassLoader
isolation using Classworlds.
@@ -323,12 +289,49 @@
</faq>
</part>
- <!--
- <faq id="">
- <question></question>
+
+ <part id="recent-changes">
+ <title>Recent Changes</title>
+
+ <faq id="classloader-property">
+ <question>Why shouldn't I use the dependency classloader override
property?</question>
<answer>
+ <p>
+ Because it isn't needed. <code>root.maven</code> is equivalent to the
project classloader.
+ While <code>root</code> is the Ant classloader, you should not load tasks
into it as it will then force itself
+ on the other plugins executed afterwards. In particular any
jakarta-commons libraries should not be in the
+ root classloader as these can clash with Jelly.
+ </p>
+ <p>
+ The correct way to use ant tasks in maven.xml or a plugin is something
like:
+ </p>
+ <source>
+<ant:taskdef name="checkstyle"
+ classname="com.puppycrawl.tools.checkstyle.CheckStyleTask">
+ <ant:classpath>
+ <ant:pathelement
location="${plugin.getDependencyPath('checkstyle:checkstyle')}"/>
+ <ant:path refid="maven.dependency.classpath"/>
+ <ant:classpath>
+<ant:taskdef>
+ </source>
+ </answer>
+ </faq>
+
+ <faq id="where-is-maven-log">
+ <question>What happened to maven.log?</question>
+ <answer>
+ <p>
+ It has been removed from <code>log4j.properties</code>. It was always
created in the directory Maven was run
+ from, and only repeated what was on the console in most cases, which was
quite annoying. You can now get all
+ the debugging information you need and more by using the -X flag to maven.
+ </p>
+ <p>
+ Of course, if you would like to write certain information to a file and
piping is not an option or you want
+ greater control over what is controlled, you can override the log4j
configuration. Refer to the log4j
+ documentation for how to override this using system properties.
+ </p>
</answer>
</faq>
- -->
+ </part>
</faqs>
-
\ No newline at end of file
+
No revision
No revision
1.63.4.5 +0 -59 maven/xdocs/reference/user-guide.xml
Index: user-guide.xml
===================================================================
RCS file: /home/cvs/maven/xdocs/reference/user-guide.xml,v
retrieving revision 1.63.4.4
retrieving revision 1.63.4.5
diff -u -r1.63.4.4 -r1.63.4.5
--- user-guide.xml 4 Mar 2004 17:45:57 -0000 1.63.4.4
+++ user-guide.xml 10 Mar 2004 11:14:03 -0000 1.63.4.5
@@ -1787,65 +1787,6 @@
</p>
</subsection>
- <subsection name="Class Loaders">
- <p>The following table shows the available classloaders :
- </p>
- <table>
- <tr>
- <th>Class loader</th>
- <th>Description</th>
- </tr>
- <tr>
- <td><default></td>
- <td>
- This class loader is used if none is specified in the dependency.
- This means that the dependency is loaded into the plugin's class
- loader, making it available to the plugin only.
- </td>
- </tr>
- <tr>
- <td><code>root</code></td>
- <td>
- This is the Ant class loader, and the most common override used in
- a plugin. Use this if you need to specify a dependency used by a
- custom Ant task used in the plugin.
- </td>
- </tr>
- <tr>
- <td><code>root.maven</code></td>
- <td>
- This is the Maven class loader. Use it if you wish to have the
- dependency available to the Maven core.
- </td>
- </tr>
- </table>
- <p>Those are also the properties that are used to control which classloader
- will be used to load the specified dependencies.
- This may be required if you are writing plugins or
- if custom scripts are defined in <code>maven.xml</code>.
- </p>
- <p>To specify a classloader for a dependency, add a section similar to
- the following to your project.xml:
- </p>
- <source><![CDATA[
-<dependency>
- <groupId>jaxb</groupId>
- <artifactId>jaxb-xjc</artifactId>
- <properties>
- <classloader>root</classloader>
- </properties>
-</dependency>
- ]]></source>
-
- </subsection>
-
</section>
- <!--
- <section name="">
- <p>
- </p>
- </section>
- -->
-
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
