Author: brett
Date: Sun Jun 5 17:20:05 2005
New Revision: 180178
URL: http://svn.apache.org/viewcvs?rev=180178&view=rev
Log:
PR: MAVEN-1612, MAVEN-1613
Submitted by: Robert Burrell Donkin
Reviewed by: Brett Porter
documentation enhancements regarding release process and plugin installation
Modified:
maven/maven-1/core/trunk/xdocs/faq.fml
maven/maven-1/core/trunk/xdocs/using/releasing.xml
Modified: maven/maven-1/core/trunk/xdocs/faq.fml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/faq.fml?rev=180178&r1=180177&r2=180178&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/faq.fml (original)
+++ maven/maven-1/core/trunk/xdocs/faq.fml Sun Jun 5 17:20:05 2005
@@ -479,6 +479,25 @@
</ul>
</answer>
</faq>
+ <faq id="finding-plugins">
+ <question>I've heard that there are lots of great plugins for Maven,
where do I find them?</question>
+ <answer>
+ <p>
+ A list of plugins is maintained by the maven team
+ <a
href='http://maven.apache.org/reference/plugins/index.html'>here</a> but
developers of third party
+ plugins are <a
href='http://maven.apache.org/reference/sharing-plugins.html'>encouraged</a> to
host
+ the plugin themselves so you may also need to search the web.
+ </p>
+ </answer>
+ </faq>
+ <faq id="install-plugins">
+ <question>How Do I Install A Third Party Plugin?</question>
+ <answer>
+ <p>
+ See <a
href='http://maven.apache.org/reference/sharing-plugins.html#Step_4__So_now_that_they_found_my_plugin__how_do_users_install_it_'>Sharing
Plugins</a>
+ </p>
+ </answer>
+ </faq>
</part>
<part id="ibiblio">
Modified: maven/maven-1/core/trunk/xdocs/using/releasing.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/using/releasing.xml?rev=180178&r1=180177&r2=180178&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/using/releasing.xml (original)
+++ maven/maven-1/core/trunk/xdocs/using/releasing.xml Sun Jun 5 17:20:05 2005
@@ -113,9 +113,20 @@
<subsection name="Cutting the Release">
<p>
As discussed previously, if you are using an SCM, you should utilise
the SCM plugin to do this as this will
- ensure a build against a clean checkout. Ideally you should also build
in a known environment each time.
+ ensure a build against a clean checkout.
+ </p>
+ <p>
+ Ideally you should also build in a known environment each time.
+ </p>
+ <p>
Pay attention to the version of Java used to compile the release: some
bytecode produced by later versions
- may be incompatible with earlier versions. Look out for warnings
provided by maven about this.
+ may be incompatible with earlier versions. Look out for warnings
provided by maven about this. Maven can
+ offer assistance: setting <code>maven.compile.target</code> of the
+ <a
href='http://maven.apache.org/reference/plugins/java/properties.html'>Java
Plugin</a> passes the
+ target JVM to the compiler.
+ Note (however) that some more subtle
+ compatibilty issues may be introduced by some modern compilers which
can be fixed only by using an older
+ compiler.
</p>
<p>
With everything together and prepared, cutting the release is quite
simple (whether the project uses SCM or not).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
