Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 6 Jul 2012 12:25:35 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <1069309190.13785.1341577535427.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1737919893.27105.1338566425303.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (CAMEL-5323) [camel-maven-plugin] Support process
 forking in camel:run goal
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5323:
-------------------------------

    Priority: Minor  (was: Major)
    
> [camel-maven-plugin] Support process forking in camel:run goal
> --------------------------------------------------------------
>
>                 Key: CAMEL-5323
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5323
>             Project: Camel
>          Issue Type: New Feature
>          Components: tooling
>    Affects Versions: 2.9.2
>            Reporter: Manuel EVENO
>            Priority: Minor
>              Labels: maven
>             Fix For: Future
>
>
> It would be nice to have the ability to fork away after a camel context has started. This is extremely useful for people that run integration tests during a maven build. They could fork an embedded camelContext (for example along with activemq:run), start their integrations tests (with soap ui), then later shut down the embedded instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira