activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r882775 - in /websites/production/activemq/content: cache/nms.pageCache nms/building.html
Date Tue, 15 Oct 2013 22:23:36 GMT
Author: buildbot
Date: Tue Oct 15 22:23:35 2013
New Revision: 882775

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/nms.pageCache
    websites/production/activemq/content/nms/building.html

Modified: websites/production/activemq/content/cache/nms.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/nms/building.html
==============================================================================
--- websites/production/activemq/content/nms/building.html (original)
+++ websites/production/activemq/content/nms/building.html Tue Oct 15 22:23:35 2013
@@ -77,17 +77,15 @@
 
 <p>Currently our main build tool for NMS is <a shape="rect" class="external-link"
href="http://nant.sourceforge.net/" rel="nofollow">NAnt</a>.</p>
 <div class="panelMacro"><table class="tipMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/check.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Setup
For *NIX Users</b><br clear="none"><ul><li>Install <a shape="rect"
class="external-link" href="http://www.mono-project.com" rel="nofollow">Mono</a></li><li>On
some operating systems (e.g. OS X), you may need to point the <b>PKG_CONFIG_PATH</b>
environment variable at the mono packages
-<div class="code panel" style="border-width: 1px;"><div class="codeHeader panelHeader"
style="border-bottom-width: 1px;"><b>Excerpt from ~/.bash_profile</b></div><div
class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
-]]></script>
+<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
+<pre>export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
+</pre>
 </div></div></li><li>Depending on your installation of <a shape="rect"
class="external-link" href="http://www.mono-project.com" rel="nofollow">Mono</a>,
you may need additional steps to get NAnt going on OS X.  The more recent versions of the
Mono installer for OS X seem to set things up properly.  However, if you are having problems
running NAnt, try the following:
 	<ul><li>download the binary of <a shape="rect" class="external-link" href="http://nant.sourceforge.net/"
rel="nofollow">NAnt</a></li><li>create a script file called nant</li><li>chmod
a+x nant</li><li>put the following into the script...
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-#!/bin/sh
+<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
+<pre>#!/bin/sh
 exec /usr/bin/mono /path/to/nant/NAnt.exe "$@"
-]]></script>
+</pre>
 </div></div></li></ul>
 	</li></ul>
 
@@ -96,12 +94,32 @@ exec /usr/bin/mono /path/to/nant/NAnt.ex
 
 <h3><a shape="rect" name="Building-BuildingNMSwithNant"></a>Building NMS
with Nant</h3>
 
-<p>You will need nant-0.91 or higher. The version 0.90 won't work.</p>
+<p>There are two steps to build the NMS project code, we'll look at each now.  </p>
+
+<h4><a shape="rect" name="Building-SettingupyourNAntRepository."></a>Setting
up your NAnt Repository.</h4>
+
+<p>Before you can build the NMS API and the various provider libraries you need to
initialize your local NAnt repository so that you have all the required dependencies available
for the provider's NAnt build scripts to pull in during their builds.  We maintain a tree
in the NMS SVN repo with all the required dependencies which allow you to easily populate
you NAnt repo.  You can check out this tree by executing the following:</p>
+
+<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
+<pre>svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/vendor/ 
+</pre>
+</div></div>
+
+<p>Now that you have the vendor tree checkout out you can install the various libaries
into you NAnt repo by running each one's build script and with the 'install' target.  You
will need nant-0.91 or higher. The version 0.90 won't work.  Let's take the NUnit testing
framework libraries as an example, you install them like so:</p>
+
+<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
+<pre>cd ./activemq-dotnet/vendor/NUnit/2.5.8
+nant install
+</pre>
+</div></div>
+
+<p>Install each of the vendor libraries using the same process and then you are ready
to build the NMS libraries.</p>
+
+<h4><a shape="rect" name="Building-BuildingtheNMSAPIandProviderlibraries."></a>Building
the NMS API and Provider libraries.</h4>
 
 <p>To build the code with Nant you will need to build the individual modules, starting
with the main NMS module first. Following are the steps needed to build all of the modules,
but depending on which provider you are using, you may only need to build the main Apache.NMS
module and then your specific provider module.  For example, if you are only working with
ActiveMQ, then you would need to build the Apache.NMS module and the Apache.NMS.ActiveMQ provider
module.  Here are the steps to build all of the modules for the trunk version.  Modify the
paths to build a particular tag release (e.g., change the <b>trunk</b> folder
to <b>tags\1.0.0</b>):</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-cd activemq-dotnetcd Apache.NMS\trunk
+<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
+<pre>cd activemq-dotnetcd Apache.NMS\trunk
 nant
 
 cd ..\..\Apache.NMS.ActiveMQ\trunk
@@ -115,79 +133,17 @@ nant
 
 cd ..\..\Apache.NMS.WCF\trunk
 nant
-]]></script>
+</pre>
 </div></div>
 <p>This will build all of the providers.  The only module that needs to be built first
is the Apache.NMS module, as all of the other provider modules depend upon that module. <b>IMPORTANT:</b>
In order to build the Apache.NMS.EMS module, you must have a licensed copy of the TIBCO.EMS.dll.
 This module is not available from The Apache Software Foundation.</p>
 <div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col
span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1"
valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif"
width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>Running
the Unit Tests</b><br clear="none">The unit tests depend on an ActiveMQ broker
running on tcp://localhost:61616 so that the test cases can connect to ActiveMQ and send and
receive messages etc.  So if you have a distribution of ActiveMQ, <a shape="rect" class="external-link"
href="http://activemq.apache.org/getting-started.html#GettingStarted-StartingActiveMQ">run
the broker</a> first before testing Apache.NMS.ActiveMQ.</td></tr></table></div>
 <p>If you want to run a build with the unit tests (assuming you have a broker running)
then type the following from the <b>trunk</b> folder of the provider module:</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-nant test
-]]></script>
+<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
panelContent">
+<pre>nant test
+</pre>
 </div></div>
 <p>Alternatively, you can use the NUnit graphical interface to load the appropriate
module's nunit project file.  Each project includes a file named Apache.NMS.<em>modulename</em>.Test.nunit,
where <em>modulename</em> matches the provider module's name (e.g., ActiveMQ,
EMS, MSMQ or WCF).  This file can be loaded into the NUnit's graphical application to run
all of the unit tests and see their output.</p>
 
-<h3><a shape="rect" name="Building-BuildingNMSusingMaven2%26nbsp%3Bisnotdirectlysupported"></a>Building
NMS using Maven 2&#160; is not directly supported</h3>
-
-<p>Maven 2 support is incomplete.&#160; Ultimately we'd prefer to use Maven to
build NMS, as then we'd have a single tool for creating distros &amp; doing builds etc.</p>
-
-<p>You can use the <a shape="rect" class="external-link" href="http://maven-csharp.javaforge.com/"
rel="nofollow">Maven C# plugin</a> to build the code if you have Maven 2.0.2 or later
installed.</p>
-
-<p>First you need to tell maven the location of the .NET environment and where to get
the Maven C# Plugins. To do that you need to edit your ~/.m2/settings.xml so that it looks
like the following. This file works on OS X - for other platforms use the correct value of
<b>dotnet.home</b> for where Mono/.Net is on your machine.</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;settings&gt;
-
-   &lt;profiles&gt;
-     &lt;profile&gt;
-      &lt;id&gt;default&lt;/id&gt;
-         &lt;properties&gt;
-           &lt;dotnet.home&gt;/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/1.0&lt;/dotnet.home&gt;
-         &lt;/properties&gt;
-
-          &lt;repositories&gt;
-              &lt;repository&gt;
-                &lt;id&gt;maven-csharp&lt;/id&gt;
-                &lt;name&gt;maven-csharp&lt;/name&gt;
-                &lt;url&gt;http://maven-csharp.javaforge.com/repo&lt;/url&gt;
-               &lt;/repository&gt;
-               &lt;repository&gt;
-                  &lt;id&gt;codehaus-snapshot&lt;/id&gt;
-                  &lt;name&gt;CodeHaus Snapshot Repo&lt;/name&gt;
-                  &lt;url&gt;http://snapshots.maven.codehaus.org/maven2&lt;/url&gt;
-               &lt;/repository&gt;
-           &lt;/repositories&gt;
-
-           &lt;pluginRepositories&gt;
-                  &lt;pluginRepository&gt;
-                    &lt;id&gt;maven-csharp-plugins&lt;/id&gt;
-                    &lt;name&gt;maven-csharp&lt;/name&gt;
-                    &lt;url&gt;http://maven-csharp.javaforge.com/repo&lt;/url&gt;
-                  &lt;/pluginRepository&gt;
-           &lt;/pluginRepositories&gt;
-
-     &lt;/profile&gt;
-   &lt;/profiles&gt;
-
-  &lt;activeProfiles&gt;
-     &lt;activeProfile&gt;default&lt;/activeProfile&gt;
- &lt;/activeProfiles&gt;
-
-  &lt;pluginGroups&gt;
-    &lt;pluginGroup&gt;com.javaforge.maven-csharp&lt;/pluginGroup&gt;
-  &lt;/pluginGroups&gt;
-
-&lt;/settings&gt;
-]]></script>
-</div></div>
-<p>Once that's done you only need to:</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-cd activemq-dotnet
-mvn install
-]]></script>
-</div></div>
-
 <h2><a shape="rect" name="Building-IDETips"></a>IDE Tips</h2>
 
 <p>If you are on windows then you probably want to use Visual Studio 2008; we highly
recommend using <a shape="rect" class="external-link" href="http://www.jetbrains.com/resharper/"
rel="nofollow">ReSharper</a> as well, - its a shame there is not a distro for OS
X and Linux <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/sad.gif"
height="20" width="20" alt="" border="0">.</p>



Mime
View raw message