Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.222.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=wO+cZ60UppPLdvTOs0/aezrzf3LLjbnnaobZzF3HEYpzuYiyBgQOxTW/+lq8wRevLM
         YBsUSjEpsk22SozB4XK5CKlAiWbUtucgRhrKGNGXukA0zXoSgKCFyi/TqeCXCG0d4JHx
         wxObbnVNXJzxURwk8VMPIjTZl69c7OVjsC7NE=
Message-ID: <4A3DB0DA.1070409@gmail.com>
Date: Sun, 21 Jun 2009 12:02:34 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: camel:run JVM arguments
References: <24121531.post@talk.nabble.com> <24128096.post@talk.nabble.com>
In-Reply-To: <24128096.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Thanks for sharing the information with the community.
Please feel free to fill a JIRA[1] or submit a patch if you don't
satisfy with current camel mvn plugin's implementation.

[1] https://issues.apache.org/activemq/browse/CAMEL

Willem

bwtaylor wrote:
> I answered my own question. It looks like camel:run uses code similar to the
> maven exec plugin and so the answer is to use the shell environment variable
> MAVEN_OPTS to pass in JVM arguments. Interestingly, it appears that
> camel:run is not forking a new JVM, but simply launching a new thread within
> the maven process.
> 
> Now if I can just figure out why TPTP is giving me "Could not find agent
> library in absolute path" when I've got the right 64bit file on the path to
> match my 64 bit JVM. Baffling.
> 
> 
> bwtaylor wrote:
>> Is there an easy way to enable debugging or profiling while using the
>> camel maven plugin to do the camel:run goal? Or more generally, can I
>> control the jvm arguments that are passed to the java command?
>>
>