camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott England-Sullivan (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5416) Camel Simple JMS Component
Date Mon, 06 Aug 2012 03:30:02 GMT


Scott England-Sullivan commented on CAMEL-5416:

Hi Babak,

-Dtest is used to specify the name of a test.  If you want to skip the tests as they are in
*fastinstall* then you would need to pass in the -Dmaven.test.skip.exec=true.

I believe to do what you are attempting though can be accomplished as follows:

mvn -Psourcecheck,fastinstall

FYI, I am also uploading a new patch to fix some errors I found while documenting.

Best Regards,
Scott ES
> Camel Simple JMS Component
> --------------------------
>                 Key: CAMEL-5416
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Scott England-Sullivan
>            Assignee: Willem Jiang
>         Attachments: CAMEL-5416.patch, camel-sjms.tar.gz, camel-sjms_wiki_documentation.txt
> I have developed a Camel JMS Component built with pure Java JMS APIs or Spring free.
 I would like to include it in the next 2.x release of Camel and am assuming that will be
> Any guidance on how much lead time would be necessary to integrate it for that release
would be appreciated (reads: when do you need the patch). :)
> _First Iteration:_
> * Full Queue and Topic Support (Durable & Non-Durable)
> * Full InOnly & InOut Support
> * Internal Connection, Session, Consumer, & Producer pooling/caching management
> * Full Asynchronous Support
> * JMS Internal Transaction Support
> _Future Iterations:_
> * Robust JMX Support
> * Camel Transaction Support
> * JTA Support (Pure Java)
> * Robust-InOnly
> * Full Migration of Core Camel-JMS Unit Tests (where applicable)
> * Batch List support
> Thanks,
> Scott ES

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message