You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@continuum.apache.org by ev...@apache.org on 2006/04/24 15:57:35 UTC
svn commit: r396555 - in
/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site: apt/
apt/guides/ apt/guides/getting-started/ apt/guides/mini/ fml/
resources/scripts/ resources/scripts/linux/
Author: evenisse
Date: Mon Apr 24 06:57:33 2006
New Revision: 396555
URL: http://svn.apache.org/viewcvs?rev=396555&view=rev
Log:
merge site from trunk
Added:
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-xmlrpc-api.apt (with props)
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/upgrade.apt (with props)
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/chkconfig_install.sh (with props)
Modified:
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/getting-started/index.apt
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/index.apt
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-configuration.apt
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-linux-boot.apt
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/release-notes.apt
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/about.fml
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/faqs.fml
maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/mvn.bat
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/getting-started/index.apt
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/getting-started/index.apt?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/getting-started/index.apt (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/getting-started/index.apt Mon Apr 24 06:57:33 2006
@@ -24,6 +24,21 @@
When Continuum is running you can access it with your browser on
{{http://localhost:8080/continuum/}} or by using the XMLRPC interface on port 8000.
+Installing Continuum as a service
+
+ If you want to install Continuum as a service in Windows, execute:
+ <<<bin/win32/InstallService.bat>>> after running <<<bin/win32/run.bat>>>. If
+ the window closes or there is no error, then the service was installed
+ successfully.
+
+ By default, the service logs on as the <Local System> account. Be sure to
+ change this to an account where you want the service to start upon login.
+
+ You can change this by going into Computer Management (right click <My Computer>
+ and select <Manage>), selecting <Services>, and double-clicking on <<<continuum>>>.
+ In the <Log On> tab, you can specify the account along with the credentials
+ required.
+
Fixing Maven and ant scripts for Windows
{{{../../faqs.html#how-does-continuum-detect-a-successful-build}How does Continuum detect a successful build?}}
@@ -37,8 +52,8 @@
If there is a <<<<modules>>>> element inside the POM continuum will try to
download the child projects by adding the module name to the end of the url.
- This makes it very easy to add a entire project to Continuum if you list all
- the child projects insode the POM.
+ This makes it very easy to add an entire project to Continuum if you list all
+ the child projects inside the POM.
If you are using ViewCVS you can add your project with a url like this:
@@ -63,7 +78,7 @@
[]
- The notifiers is configured inside the <<<<ciManagement>>>> section of the POM
+ The notifiers are configured inside the <<<<ciManagement>>>> section of the POM
like this:
+--+
@@ -107,10 +122,10 @@
* Adding Maven 1 Projects
- Adding a Maven 1 it pretty much like adding a Maven 2 project, pass it an URL
+ Adding a Maven 1 project is pretty much like adding a Maven 2 project, pass it a URL
to a POM with SCM information and Continuum will add the projects.
- There are is a caveat though: The POM cannot extend a parent POM. When
+ There is a caveat though: The POM cannot extend a parent POM. When
Continuum is downloading the POM it won't know how to find the parent POMs.
The best way to use Continuum with Maven 1 projects is to give Continuum the
root POM of your projects only and then have a special goal in the root
@@ -122,7 +137,7 @@
When adding Ant projects you have to specify the project's name, SCM URL,
version and the targets to execute.
- <NOTE:> The SCM URL is a Maven SCM URL. Here's an example of what an
+ <NOTE:> The SCM URL is a {{{http://maven.apache.org/scm/scm-url-format.html}Maven SCM URL}}. Here's an example of what an
SCM URL looks like:
<<<scm:svn:http://svn.apache.org/repos/asf/maven/continuum/trunk>>>
@@ -135,6 +150,31 @@
<NOTE:> The SCM URL is a Maven SCM URL. Here's an example of what an
SCM URL looks like:
<<<scm:svn:http://svn.apache.org/repos/asf/maven/continuum/trunk>>>
+
+ To specify the shell script to be executed, click on the shell project and
+ click "Add" under the "Build Definitions" section. This script should <<at
+ least>> be able to run Maven.
+
+ Here is a sample batch script that calls <<<mvn.bat>>> in a Windows environment:
+
++--+
+@echo off
+
+cmd /C mvn.bat MAVEN PARAMETERS HERE
+if ERRORLEVEL 1 goto error
+goto end
+
+:error
+exit 1
+
+:end
+exit 0
++--+
+
+ The script executes Maven and obtains the exit code from it. You may add
+ post-build tasks to the <<<:error>>> and/or <<<:end>>> sections provided they
+ are placed before the <<<exit>>> statements. Pre-build tasks should be added
+ before the call to <<<mvn.bat>>>.
Building Projects
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/index.apt
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/index.apt?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/index.apt (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/index.apt Mon Apr 24 06:57:33 2006
@@ -18,7 +18,7 @@
* {{{mini/guide-linux-boot.html}Guide to Configuring Continuum to start automatically on Linux}}
- * {{{mini/guide-soap-api.html}Guide to using the SOAP API}}
+ * {{{mini/guide-xmlrpc-api.html}Guide to using the XML-RPC API}}
* Introductory Material
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-configuration.apt
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-configuration.apt?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-configuration.apt (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-configuration.apt Mon Apr 24 06:57:33 2006
@@ -22,20 +22,20 @@
* <<<from-mailbox>>> and <<<from-name>>>: The mailbox and name that will be
set as the <<<From>>> header for all mails sent. It is important to ensure
that the mailbox is a real account as most SMTP servers will verify that
- the mailbox actually exists before accepting the mail. If the from mailbox
+ the mailbox actually exists before accepting the mail. If the <<<from-mailbox>>>
is empty or not specified the nag email address for the project will be
used.
* <<<timestamp-format>>>: This is the timestamp format used for the dates in
email messages.
- * The recipient source. This is the component that decides who should receive
- the email. The only thing that can be configured here is a address that will
+ * The <<<RecipientSource>>> is the component that decides who should receive
+ the email. The only thing that can be configured here is an address that will
be used as the recipient for all email sent. This configuration is mostly
useful for people who want to make sure all email is sent to a specific
account during testing or development.
- * The mail sender is the component that will send the email to the SMTP
+ * The <<<MailSender>>> is the component that will send the email to the SMTP
server. The two properties that can be configured are:
* <<<smtp-host>>>: The SMTP host. Make sure that this host will accept email.
@@ -78,7 +78,7 @@
This is a example configuration on how to configure Jetty with one normal HTTP
listener and one proxy HTTP listener. With this configuration Jetty will
listen on two ports; 8080 and 8090. Continuum can be used from either
- http://localhost:8080 or http://www.company.com/continuum. Note that the
+ <<<http://localhost:8080/continuum>>> or <<<http://www.company.com/continuum>>>. Note that the
proxying listener will make Continuum write out URLs with the configured proxy
host and port.
@@ -107,9 +107,9 @@
</service>
+----+
-** Example Apache Configuration
+** Example Apache httpd Configuration
- This is a example configuration on how to configure Apache to work as a front
+ This is a example configuration on how to configure Apache httpd to work as a front
end to Continuum. Make sure <<<mod_proxy>>> is installed and loaded and that
Jetty is configured with a proxy HTTP listener on the proxy port.
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-linux-boot.apt
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-linux-boot.apt?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-linux-boot.apt (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-linux-boot.apt Mon Apr 24 06:57:33 2006
@@ -9,32 +9,34 @@
* Introduction
- This document explains how to setup continuum to start automatically (when the machine boots)
- in linux. This is a procedure quite tipical for a linux system administrator, the
+ This document explains how to setup Continuum to start automatically (when the machine boots)
+ on linux. This is a procedure quite typical for a linux system administrator, the
purpose of this document is to help you in case you don't have a linux sysadmin
at hand.
This document is based on Debian GNU/Linux, all concepts should apply to other distributions
- and all procedures (tipically with some slight modificacion on directories paths) should apply.
+ and all procedures (typically with some slight modification on directories paths) should apply.
* Prerequisites
- * Download continuum from {{{../../download.html}here}}.
+ * Download Continuum from {{{../../download.html}here}}.
- * extract the archive in <<</usr/local>>>
+ * Extract the archive in <<</usr/local>>>
-* Configuring continuum in init
+* Configuring Continuum in init
- Since the continuum linux script bin/linux/run.sh understands the same arguments as linux boot scripts,
- there is no need to write a particular startup script to add continuum to the linux boot process.
+ Since the Continuum linux script bin/linux/run.sh understands the same arguments as linux boot scripts,
+ there is no need to write a particular startup script to add Continuum to the linux boot process.
All you need to do, as root, is:
+** In a Debian-based system
+
+--+
ln -s /usr/local/continuum-[VERSION]/bin/linux/run.sh /etc/init.d/continuum
+--+
- At this point you have continuum ready to be symlinked from different runlevels. This might
- sound a bit esoteric, but it is not, you find very fast these words as soon as you start reading
+ At this point you have Continuum ready to be symlinked from different runlevels. This might
+ sound a bit esoteric, but it is not, you will find these words very fast as soon as you start reading
about the init process. Fortunately, Debian GNU/Linux comes with a very handy utility to create this
links, just run as root:
@@ -42,7 +44,7 @@
update-rc.d -n continuum defaults 80
+--+
- If just copypasted this command, you will see something like this:
+ If you run this command, you will see something like this:
+--+
Adding system startup for /etc/init.d/continuum ...
@@ -55,6 +57,15 @@
/etc/rc5.d/S80continuum -> ../init.d/continuum
+--+
- What you see is the symlinks that would be created. The above command didn't do anything that's
- because the <<<-n>>> switch, remove it to get the real links creted.
+ What you see is the symlinks that would be created. The above command didn't do anything
+ because of the <<<-n>>> switch, remove it to get the real links created.
+
+** In a RedHat-based system
+
+ Configuring Continuum in a RedHat-based system (like Fedora Core) is slightly different: Instead of
+ running update-rc.d, you need to add a new service using chkconfig. And in order to add Continuum to chkconfig,
+ it is necessary to add some comments to the /etc/rc.d/init.d/continuum script and run a couple of commands; these
+ tasks are automatically executed by running the chkconfig_install.sh script available {{{../../scripts/linux/chkconfig_install.sh}here}}.
+
+
Added: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-xmlrpc-api.apt
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-xmlrpc-api.apt?rev=396555&view=auto
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-xmlrpc-api.apt (added)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-xmlrpc-api.apt Mon Apr 24 06:57:33 2006
@@ -0,0 +1,109 @@
+ ------
+ Guide to using the XML-RPC API
+ ------
+ Emmanuel Venisse
+ ------
+ April 24, 2006
+
+Getting Started
+
+ Continuum has a XML-RPC API which makes it easy to add, remove, view and manipulate
+ builds from within your applications. Continuum includes a client class to access this
+ API. Alternatively, you may generate a client from favorite XML-RPC toolkit
+ (such as the toolkits for PERL or .NET). If you are using a client other than the one
+ mentioned below, you'll ned to write a code similar to the one in
+ {{{http://svn.apache.org/viewcvs.cgi/maven/continuum/tags/continuum-1.0.3/continuum-rpc-client/src/main/java/org/apache/maven/continuum/rpc/ProjectsReader.java?rev=395968&view=markup}ProjectsReader}}.
+
+ The API provides the following operations:
+
+ * addProject
+
+ * editProject
+
+ * buildProject
+
+ * refreshProject
+
+ * readProjects
+
+Using the Java Client
+
+* Creating a Client
+
+ The jar to use is {{{http://www.ibiblio.org/maven2/org/apache/maven/continuum/continuum-rpc-client/1.0.3/continuum-rpc-client-1.0.3.jar}here}}.
+ You can include it in your classpath or in your pom if you make your client with maven2.
+
++--+
+import org.apache.maven.continuum.model.project.Project
+import org.apache.maven.continuum.rpc.ProjectsReader;
+...
+
+String url = "http://localhost:8000/continuum";
+ProjectsReader pr = new ProjectsReader( new URL( address ) );
++--+
+
+* Adding a Project
+
++--+
+Project project = new Project();
+project.setExecutorId( "maven2" );
+project.setScmUrl( "scm:svn...." );
+
+pr.addProject( project );
++--+
+
+ The project type tells Continuum what type of project to expect. Valid values are
+ "ant", "shell", "maven-1", and "maven2".
+
+* Getting a Project
+
++--+
+Project project = new Project();
+project.setId( projectId );
+
+pr.refreshProject( project );
++--+
+
+* Getting the projects list
+
++--+
+projects = pr.readProjects();
+
+for ( int i = 0; i < projects.length; i++ )
+{
+ System.out.println( projects[i] + " - Name=" + projects[i].getName() + " :" + projects[i].getState() );
+}
++--+
+
+* Building a Project
+
++--+
+Project project = new Project();
+project.setId( projectId );
+
+pr.buildProject( project );
++--+
+
+* Project State
+
+ In one of the above code snippets, you see that we can check the build state.
+ The build state can be one of several values:
+
+*---------*------------------------+
+| 1 or 10 | New Build |
+*---------*------------------------+
+| 2 | Successful Build |
+*---------*------------------------+
+| 3 | Failed Build |
+*---------*------------------------+
+| 4 | Error building |
+*---------*------------------------+
+| 6 | Build in process |
+*---------*------------------------+
+| 7 | Checking out from SCM |
+*---------*------------------------+
+| 8 | Updating from SCM |
+*---------*------------------------+
+| 9 | Warned Build |
+*---------*------------------------+
+
Propchange: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-xmlrpc-api.apt
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/guides/mini/guide-xmlrpc-api.apt
------------------------------------------------------------------------------
svn:keywords = "Author Date Id Revision"
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/release-notes.apt
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/release-notes.apt?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/release-notes.apt (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/release-notes.apt Mon Apr 24 06:57:33 2006
@@ -22,8 +22,6 @@
* Added an internal maven repository for built projects
- * Added a servlet browser to allow the navigation of all project files
-
* Improved the project build for projects with multiple build definitions
* Improved maven2 setings/profiles loading
Added: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/upgrade.apt
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/upgrade.apt?rev=396555&view=auto
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/upgrade.apt (added)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/upgrade.apt Mon Apr 24 06:57:33 2006
@@ -0,0 +1,58 @@
+ ------
+ Upgrade
+ ------
+ Emmanuel Venisse
+ Dan T. Tran <da...@apache.org>
+ ------
+ April 24, 2006
+
+Upgrade
+
+ The following contains migration instructions between Continuum releases.
+
+
+* 1.0.2 to 1.0.3
+
+ * Shutdown your Continuum 1.0.2
+
+ * Install your Continuum 1.0.3
+
+ * Initialize your Continuum 1.0.3 by starting it from command line, wait for it to complete the initialization,
+ and then shut it down.
+
+ * Replace Continuum 1.0.3's <<<apps/continuum/database>>> with Continuum 1.0.2's <<<apps/continuum/database>>>.
+
+ * Start your Continuum 1.0.3.
+
+ * Login and change "Working Directory" and "Build Output Directory" in the Configuration screen, if needed. If you use default
+ values for these directories, you only need to copy them from <<<apps/continuum/>>>. A best practice is to use them out of
+ Continuum sub-directories.
+
+* 1.0.1 to 1.0.2
+
+ Since there are no changes in the database schema, the migration steps are mainly to replace Continuum 1.0.2's database
+ with Continuum 1.0.1's database. Here are detailed instructions:
+
+ * Shutdown your Continuum 1.0.1.
+
+ * Install your Continuum 1.0.2
+
+ * Initialize your Continuum 1.0.2 by starting it from command line, wait for it to complete the initialization,
+ and then shut it down.
+
+ * Replace Continuum 1.0.2's <<<apps/continuum/conf/application.xml>>> with Continuum 1.0.1's <<<apps/continuum/conf/application.xml>>>.
+ Edit application.xml and replace any reference of 1.0.1 with 1.0.2.
+
+ * Replace Continuum 1.0.2's <<<apps/continuum/database>>> with Continuum 1.0.1's <<<apps/continuum/database>>>.
+
+ * Start your Continuum 1.0.2.
+
+ * Login and change "Working Directory" and "Build Output Directory" if needed. If you use default values for these directories,
+ you only need to copy them from <<<apps/continuum/>>>.
+
+ []
+
+ [Note:] If you have Continuum running as UNIX daemon or Windows NT service, make sure you modify the configuration
+ to point to new Continuum.
+
+
Propchange: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/upgrade.apt
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/apt/upgrade.apt
------------------------------------------------------------------------------
svn:keywords = "Author Date Id Revision"
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/about.fml
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/about.fml?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/about.fml (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/about.fml Mon Apr 24 06:57:33 2006
@@ -60,7 +60,7 @@
in the <i>Channel</i> box).
</p>
<p>
- Please remember that is is a preview release, so please be patient with features that are not yet implemented,
+ Please remember that it is a preview release, so please be patient with features that are not yet implemented,
and be prepared to do some research and to help out yourself wherever possible.
</p>
</answer>
@@ -93,18 +93,33 @@
</p>
<p>
To checkout the continuum-site project from the ASF Subversion repository, download the Subversion client for
- your platform and run: <code>svn co http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site</code>
+ your platform and run:
+ <source>
+svn co https://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site
+ </source>
</p>
<p>
To build the continuum-site project you will need to use Maven 2. You can download Maven 2 from the <a
href="http://maven.apache.org/maven2/download.html">Downloads page on the Maven 2 project site</a>. Once you
have installed Maven 2 and added it to your <code>PATH</code>, you can build the Continuum project site by
- executing the <code>site:site</code> goal with the following command: <code>m2 site:site</code>.
+ executing the <code>site:site</code> goal with the following command:
+ <source>
+mvn site:site
+ </source>
After executing the <code>site:site</code> goal, the Continuum site will be stored in the
<code>target/site</code> directory.
</p>
<p>
- Once you have updated the documentation, generate a patch by running <code>svn diff > site-patch.txt</code>. Create a
+ If you receive an error resolving the artifact <code>continuum-parent</code>, download the parent pom.xml from <a
+ href="http://svn.apache.org/repos/asf/maven/continuum/trunk/pom.xml">here</a> and place it in the directory above your
+ <code>continuum-site</code> directory. Then try the build again.
+ </p>
+ <p>
+ Once you have updated the documentation, generate a patch by running
+ <source><![CDATA[
+svn diff > site-patch.txt
+ ]]></source>
+ Create a
new issue in the Continuum JIRA project, and attach your patch to this issue. Before submitting the patch, make sure
to build the Continuum site locally and proofread for any typos.
</p>
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/faqs.fml
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/faqs.fml?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/faqs.fml (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/fml/faqs.fml Mon Apr 24 06:57:33 2006
@@ -6,7 +6,7 @@
<p>
If you want to add a project that extends an other, you must add the parent project.
When you add a project with sub-projects, Continuum will add all sub-projects, so you
- need to provide an URL instead to uploading a POM so that Continuum can find all sub-projects.
+ need to provide a URL instead of uploading a POM so that Continuum can find all sub-projects.
</p>
</answer>
</faq>
@@ -14,9 +14,9 @@
<question>How can I add my maven 2 project with modules?</question>
<answer>
<p>
- If your project has modules, you need to provide an URL instead of uploading a POM.
+ If your project has modules, you need to provide a URL instead of uploading a POM.
When you add a project with modules, Continuum will add all sub-projects, and this
- only works by submitting an URL.
+ only works by submitting a URL.
</p>
</answer>
</faq>
@@ -27,24 +27,24 @@
Continuum uses the command line return code for detecting a successful or failed execution.
</p>
<p>
- If you use maven or ant, you need to add at the end of maven.bat and ant.bat, the following line :
+ If you use maven or ant, you need to add the following line at the end of <code>maven.bat</code> and <code>ant.bat</code> :
</p>
<source>
if "%MAVEN_TERMINATE_CMD%" == "on" exit %ERRORLEVEL%
</source>
<p>
- If your bat file contains at the end an exit /B, this line must be copy before it.
+ If your bat file contains an <code>exit /B</code> at the end, this line must be inserted before it.
</p>
<p>
<b>This part is for Continuum < 1.0.2</b>
- You must add too, at the begin of $CONTINUUM/bin/win32/run.bat, the following lines if you run Continuum from command line :
+ You must also add the following lines at the begin of <code>$CONTINUUM/bin/win32/run.bat</code>, if you run Continuum from the command line :
</p>
<source>
@echo off
set MAVEN_TERMINATE_CMD=on
</source>
<p>
- or this line in wrapper.conf, if you run Continuum as a service (works too with command line) :
+ or this line in <code>wrapper.conf</code>, if you run Continuum as a service (works with command line too) :
</p>
<source>
set.MAVEN_TERMINATE_CMD=on
@@ -58,14 +58,14 @@
<question>Can i use file protocol in Add Project view?</question>
<answer>
<p>
- File protocol is disabled by default for security reasons. You can allow it in $CONTINUUM_HOME/apps/continuum/conf/application.xml
+ File protocol is disabled by default for security reasons. You can allow it in <code>$CONTINUUM_HOME/apps/continuum/conf/application.xml</code>
</p>
<p>
Uncomment the following line :
</p>
- <source><![CDATA[
- <allowedScheme>file</allowedScheme>
- ]]></source>
+ <source>
+<allowedScheme>file</allowedScheme>
+ </source>
</answer>
</faq>
<faq id="i-m-running-on-windows-and-continuum-cant-log-to-my-cvs-repository-whats-going-on">
@@ -73,14 +73,14 @@
<answer>
<p>
You're probably running the CVSNT client, or another application based on it, like TortoiseCVS. CVSNT stores passwords in the registry,
- rather than the ~/.cvspass file. You'll need to issue the following command manually (but only once), with the appropriate information filled in:
+ rather than the <code>~/.cvspass</code> file. You'll need to issue the following command manually (but only once), with the appropriate information filled in:
</p>
<source>
cvs -d :pserver:account@cvsserver:2401:/rootfolder login
</source>
<p>
Also, note that the login will only be saved for the particular user who typed it. If you're running Continuum as a service, double-check the user
- it is running as, and make sure that you run cvs login as that user.
+ it is running as, and make sure that you run <code>cvs login</code> as that user.
</p>
</answer>
</faq>
@@ -97,7 +97,7 @@
</answer>
</faq>
<faq id="builds-keep-failing-because-continuum-cant-checkout-sources">
- <question>Why Continuum builds keep failing with password is required even if I'm using anonymous or no password in CVS?</question>
+ <question>Why does Continuum builds keep failing with password is required even if I'm using anonymous or no password in CVS?</question>
<answer>
<p>
If you keep getting this build error on your projects:
@@ -128,6 +128,125 @@
</p>
</answer>
</faq>
+ <faq id="How-can-I-run-continuum-on-a-different-port">
+ <question>How can I run Continuum on a different port? I already have application X running on port 8000/8080.</question>
+ <answer>
+ <p>
+ Continuum uses two ports. Port 8000 is used for XML-RPC calls and port 8080 is used by the instance of Jetty that supplies the web interface for Continuum.
+ </p>
+ <p>
+ If you have another application already running on port 8000/8080, you will get an exception when you start Continuum.
+ If you want to change the port that Continuum uses you should edit the file <code>apps/continuum/conf/application.xml</code>.
+ Find the following section in that file:
+ </p>
+ <source>
+<application>
+ ...
+ <services>
+ <service>
+ <id>jetty</id>
+ <configuration>
+ <webapps>
+ <webapp>
+ <file>${plexus.home}/lib/continuum-web-1.0.2.jar</file>
+ <context>/continuum</context>
+ <extraction-path>${plexus.home}/webapp</extraction-path>
+ <listeners>
+ <http-listener>
+ <port>8080</port>
+ </http-listener>
+ <!--
+ <proxy-http-listener>
+ <port>8090</port>
+ <proxy-host>localhost</proxy-host>
+ <proxy-port>80</proxy-port>
+ </proxy-http-listener>
+ -->
+ </listeners>
+ </webapp>
+ </webapps>
+ </configuration>
+ </service>
+ <service>
+ <id>xml-rpc</id>
+ <configuration>
+ <xmlrpc>
+ <port>8000</port>
+ </xmlrpc>
+ <handlers>
+ <handler>
+ <role>org.apache.maven.continuum.xmlrpc.ContinuumXmlRpc</role>
+ <name>continuum</name>
+ </handler>
+ </handlers>
+ </configuration>
+ </service>
+ </services>
+ ...
+</application>
+ </source>
+ <p>
+ Change the appropriate <code><port></code> elements to the port numbers you want for jetty and xml-rpc.
+ You need to restart Continuum for the changes to take effect.
+ </p>
+ </answer>
+ </faq>
+ <faq id="build-entire-project-recursively-from-parent">
+ <question>How can I build the entire project recursively from the parent?</question>
+ <answer>
+ <p>
+ If you want to build recursively from the parent, you have to remove the <code>--non-recursive</code> or <code>-N</code> argument under the
+ "Build Definitions" section of your parent project.
+ </p>
+ <p>
+ Ensure that your entire project can be checked out using the SCM URL in your parent project.
+ </p>
+ <p>
+ For CVS users who have each child project in a separate module, you have several options:
+ <p>
+ <ui>
+ <li>Refactor the CVS directory structure to a more standard one (i.e. a module with the parent POM at the base and child projects as subdirectories)</li>
+ <li>Keep the structure and create a new module that contains a parent POM and a list of symbolic links to your actual CVS modules</li>
+ </ui>
+ </p>
+ These options ensure that your child projects will not be checked out into separate numbered working directories. Instead, they will be checked out
+ correctly under a single working directory.
+ </p>
+ </answer>
+ </faq>
+ <faq id="cant-run-on-macosx">
+ <question>Why $CONTINUUM/bin/macosx/run.sh doesn't work for me?</question>
+ <answer>
+ <p>
+ On some MacOS X version, The <a href="http://wrapper.tanukisoftware.org/">Java Service Wrapper</a> used by Continuum doesn't work with an error like this:
+ </p>
+ <source>
+$ run.sh console
+Running continuum...
+wrapper | --> Wrapper Started as Console
+dyld: lazy symbol binding failed: Symbol not found: _ftime
+ </source>
+ <p>
+ You can run <b>$CONTINUUM/bin/plexus.sh</b> instead.
+ </p>
+ </answer>
+ </faq>
+ <faq id="cant-run-on-solaris">
+ <question>Why $CONTINUUM/bin/solaris/run.sh doesn't work for me?</question>
+ <answer>
+ <p>
+ This script is only for sparc processor. If you have an Intel processor, you must run <b>$CONTINUUM/bin/plexus.sh</b> instead.
+ </p>
+ </answer>
+ </faq>
+ <faq id="add-an-scm-hook-script">
+ <question>How can I build projects with a scm post-commit hook?</question>
+ <answer>
+ <p>
+ If your SCM support hook scripts, you'll need to write an <a href="guides/mini/guide-xmlrpc-api.html">xml-rpc client</a> for Continuum and call it in your post-commit script.
+ </p>
+ </answer>
+ </faq>
</part>
</faqs>
Added: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/chkconfig_install.sh
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/chkconfig_install.sh?rev=396555&view=auto
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/chkconfig_install.sh (added)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/chkconfig_install.sh Mon Apr 24 06:57:33 2006
@@ -0,0 +1,51 @@
+#! /bin/sh
+#
+# chkconfig_install.sh - install Continuum on a chkconfig-bases system
+#
+# Author: Felipe Leme <fe...@apache.org>
+#
+
+# figure out what's Continuum's directory
+CONTINUUM_HOME=`dirname $0`
+cd ${CONTINUUM_HOME}
+CONTINUUM_HOME=`pwd`
+
+INITD_SCRIPT=/etc/rc.d/init.d/continuum
+
+if [ -f ${INITD_SCRIPT} ]
+then
+ echo "File ${INITD_SCRIPT} already exists. Please remove it and try again."
+ exit 1
+fi
+
+echo "Creating file ${INITD_SCRIPT}"
+cat >> ${INITD_SCRIPT} <<EOF
+#! /bin/sh
+# chkconfig: 345 90 10
+# description: Maven Continuum server
+
+# uncoment to set JAVA_HOME as the value present when Continuum installed
+#export JAVA_HOME=${JAVA_HOME}
+
+if [ -z "\${JAVA_HOME}" ]
+then
+ echo "Cannot manage Continuum without variable JAVA_HOME set"
+ echo " (try to set it on file ${INITD_SCRIPT})"
+ exit 1
+fi
+# run Continuum as root
+cd ${CONTINUUM_HOME}
+./run.sh \$*
+# run Continuum as user _continuum_user_
+#su - _continuum_user_ -c "cd ${CONTINUUM_HOME}; ./run.sh \$*"
+EOF
+chmod +x ${INITD_SCRIPT}
+
+echo "Adding Continuum to chkconfig"
+chkconfig --add continuum
+
+echo "Enabling Continuum on chkconfig"
+chkconfig continuum on
+echo "Continuum set to start on run levels 3, 4 and 5."
+echo "To start continuum now, run 'service continuum start'"
+
Propchange: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/chkconfig_install.sh
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/linux/chkconfig_install.sh
------------------------------------------------------------------------------
svn:keywords = "Author Date Id Revision"
Modified: maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/mvn.bat
URL: http://svn.apache.org/viewcvs/maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/mvn.bat?rev=396555&r1=396554&r2=396555&view=diff
==============================================================================
--- maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/mvn.bat (original)
+++ maven/continuum/branches/continuum-1.0.x/continuum-site/src/site/resources/scripts/mvn.bat Mon Apr 24 06:57:33 2006
@@ -38,11 +38,11 @@
@REM Execute a user defined script before this one
if exist "%HOME%\mavenrc_pre.bat" call "%HOME%\mavenrc_pre.bat"
+set ERROR_CODE=0
+
@REM set local scope for the variables with windows NT shell
if "%OS%"=="Windows_NT" @setlocal
-set ERROR_CODE=0
-
@REM ==== START VALIDATION ====
if not "%JAVA_HOME%" == "" goto OkJHome
@@ -67,7 +67,7 @@
:chkMHome
if not "%M2_HOME%"=="" goto valMHome
-if "%OS%"=="Windows_NT" SET M2_HOME=%~dps0\..
+if "%OS%"=="Windows_NT" SET M2_HOME=%~dp0\..
if not "%M2_HOME%"=="" goto valMHome
echo.