Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 544B9200B91 for ; Thu, 29 Sep 2016 09:20:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4A7A6160AE3; Thu, 29 Sep 2016 07:20:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 66C5E160AD7 for ; Thu, 29 Sep 2016 09:20:03 +0200 (CEST) Received: (qmail 26256 invoked by uid 500); 29 Sep 2016 07:20:02 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 26247 invoked by uid 99); 29 Sep 2016 07:20:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Sep 2016 07:20:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 1C9A4180538 for ; Thu, 29 Sep 2016 07:20:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id xlkrwlSsZmiT for ; Thu, 29 Sep 2016 07:19:59 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 92E505FAEA for ; Thu, 29 Sep 2016 07:19:59 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 83557E015D for ; Thu, 29 Sep 2016 07:19:58 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 464F33A0796 for ; Thu, 29 Sep 2016 07:19:56 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r998535 - in /websites/production/camel/content: building.html cache/main.pageCache Date: Thu, 29 Sep 2016 07:19:56 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160929071957.464F33A0796@svn01-us-west.apache.org> archived-at: Thu, 29 Sep 2016 07:20:04 -0000 Author: buildbot Date: Thu Sep 29 07:19:55 2016 New Revision: 998535 Log: Production update by buildbot for camel Modified: websites/production/camel/content/building.html websites/production/camel/content/cache/main.pageCache Modified: websites/production/camel/content/building.html ============================================================================== --- websites/production/camel/content/building.html (original) +++ websites/production/camel/content/building.html Thu Sep 29 07:19:55 2016 @@ -87,10 +87,10 @@

Building Camel from Source

Camel uses Maven as its build and management tool. If you don't fancy using Maven you can use your IDE directly or Download a distribution or JAR.

Prequisites

Required:

  • Download and install Maven
    (Maven 3.1.1 or newer is required to build Camel 2.14 onwards)
    (Maven 3.2.5 or newer is required to build Camel 2.18 onwards) 
  • Get the latest Source
  • Java
    (1.7 or 1.8 to build Camel 2.14 onwards)
    (1.8 to build Camel 2.18 onwards) 

Optional:

  • Prince should be in the executable PATH to generate the PDF documentation

Maven options

To build camel maven has to be configured to use more memory

Unix/Linux/Mac
-
Windows
-

A normal build

-
Cloning the Git Repository 

Either follow instructions about getting the latest source, or clone the Git repository with Eclipse by selecting "File -> Import -> Git / Projects from Git" and "Clone URI". Provide all repository details in the import wizard and clone the repository into a directory outside of the Eclipse workspace. Once cloning has completed, exit the import project wizard (i.e. simply select cancel when asked to select "Wizard for project import").

Import Maven Projects

Import Camel projects as Maven projects using m2e by selecting "File -> Import -> Maven -> Existing Maven Projects". Point the wizard to the root directory of the cloned repository. Eclipse will analyze all Camel projects and eventually present the following summary:

Simply confirm the import of all projects by clicking "Finish". The import process will create Eclipse projects and automatically set up build paths using dependency details provided by the pom.xml files. Once completed, all Camel projects will be available in your workspace:

maven-eclipse-plugin

The maven-eclipse-plugin can be used to generate the .classpath/.project/.settings file that Eclipse need. To do this, run:

+
Cloning the Git Repository 

Either follow instructions about getting the latest source, or clone the Git repository with Eclipse by selecting "File -> Import -> Git / Projects from Git" and "Clone URI". Provide all repository details in the import wizard and clone the repository into a directory outside of the Eclipse workspace. Once cloning has completed, exit the import project wizard (i.e. simply select cancel when asked to select "Wizard for project import").

Import Maven Projects

Import Camel projects as Maven projects using m2e by selecting "File -> Import -> Maven -> Existing Maven Projects". Point the wizard to the root directory of the cloned repository. Eclipse will analyze all Camel projects and eventually present the following summary:

Simply confirm the import of all projects by clicking "Finish". The import process will create Eclipse projects and automatically set up build paths using dependency details provided by the pom.xml files. Once completed, all Camel projects will be available in your workspace:

maven-eclipse-plugin

The maven-eclipse-plugin can be used to generate the .classpath/.project/.settings file that Eclipse need. To do this, run:

or

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