You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@myfaces.apache.org by gr...@apache.org on 2012/11/19 22:46:30 UTC
svn commit: r1411440 - /myfaces/site/trunk/src/site/xdoc/buildhowto.xml
Author: grantsmith
Date: Mon Nov 19 21:46:29 2012
New Revision: 1411440
URL: http://svn.apache.org/viewvc?rev=1411440&view=rev
Log:
Ancient Ant build instructions removed and replaced with a link to the current wiki page for Maven builds
Modified:
myfaces/site/trunk/src/site/xdoc/buildhowto.xml
Modified: myfaces/site/trunk/src/site/xdoc/buildhowto.xml
URL: http://svn.apache.org/viewvc/myfaces/site/trunk/src/site/xdoc/buildhowto.xml?rev=1411440&r1=1411439&r2=1411440&view=diff
==============================================================================
--- myfaces/site/trunk/src/site/xdoc/buildhowto.xml (original)
+++ myfaces/site/trunk/src/site/xdoc/buildhowto.xml Mon Nov 19 21:46:29 2012
@@ -22,77 +22,10 @@
<body>
<section name="Overview">
<p>
- MyFaces uses Ant to build from the source. Click <a href="http://ant.apache.org">here</a> for more information on
- Apache Ant. These instructions also assume you have already checked out the source code. If you have not done this, please
- see the SVN instructions <a href="svn.html">here</a>.
- </p>
- <p>
- There are two ways to build MyFaces. The first is from the "top level" build directory which is used to build "all" of the
- subprojects in the correct order. The other method is to build one or more subprojects directly.
+ Please refer to <a href="https://cwiki.apache.org/MYFACES/build-myfaces-core-from-source-code-using-maven.html">this page</a> for more information on
+ how to build from source, using Maven.
</p>
</section>
- <section name=""One Build To Rule Them All"">
- <p>
- MyFaces uses a single build file to build all of the subprojects. This build file is available in all of the subprojects
- and is shared through the magic of svn:externals. If you are interested in building everything then you want to execute
- the build from the "top level" build directory. <em>This is the build directory immediately under the directory you check
- out the <code>current</code> SVN code to.</em>
- </p>
- <p>
- Most of the targets in the build script have an "all" version that can be used to build all of the subprojects:
- <code>clean-all, javadoc-all, dist-all </code> etc.
- </p>
- <source xml:space="preserve">
- svn co https://svn.apache.org/repos/asf/myfaces/current myfaces-current
- cd myfaces-current/build
- ant download-dependencies dist-all
- </source>
- <p>
- You can also build the subprojects individually by using the build file contained in the relevant subproject's build directory.
- There are some restrictions on this, however, as not all of the subprojects can be built independently. For certain subprojects,
- the order is important.
- </p>
- <p>
- Example: You want to build myfaces-impl.jar. This requires the API to compile so you would need to build the API subproject first.
- </p>
- <source xml:space="preserve">
- svn co https://svn.apache.org/repos/asf/myfaces/current myfaces-current
- cd myfaces-cuurent/api/build
- ant download-dependencies
- ant dist
- cd ../../
- cd impl
- ant dist
- </source>
- </section>
- <section name="Dependencies">
- <p>
- There are several third party JAR files that MyFaces depends on (for a complete list see the comments in the build.xml file.)
- The simplest way to obtain these jar files is to run <code>ant download-dependencies</code> from the top level build directory.
- This will create a lib directory that will automatically be used by the Ant script when building. Normally this is a one-time
- step but you may want to occassionally run this target to make sure the dependencies have not changed (especially if you
- are unable to build all of a sudden.)
- </p>
- <p>
- It is not required that you use the <code>download-dependencies</code> target. The <code>build.default.properties</code> file
- contains a list of the jar file dependencies. By default it points to the top level lib directory. So to use your own local
- JAR files you have three options:
- </p>
- <ul>
- <li>
- Create a top level lib directory and copy your jars into it (editing the <code>build.default.properties</code> file if
- necessary.)
- </li>
- <li>
- Create/edit the <code>build.properties</code> file in your home directory so that each entry in <code>
- build.default.properties</code> file is accounted for and points to the appropriate location on your machine.
- </li>
- <li>
- Create/edit the <code>build.local.properties</code> file in your build directory so that each entry in <code>
- build.default.properties</code> file is accounted for and points to the appropriate location on your machine.
- </li>
- </ul>
- </section>
</body>
</document>
\ No newline at end of file