[ecf-dev] JMS provider update

[Scott Lewis <slewis@xxxxxxxxxxxxx>]

Hi Folks,

I've created an enhancement to update our ActiveMQ/JMS provider (located 
at http://github.com/ECF) to version ActiveMQ version 5.8.0 (it's 
currently 5.3.2) [1].  I've started work on this myself, but please add 
yourself to the bug if you are interested in helping out.

As part of this, I would like to also move to using/consuming from Orbit 
the javax.jms API implementation (version 1.1) rather than including it 
as a lib within the org.eclipse.ecf.provider.jms bundle.  The only 
reason was it was included previously was that the javax.jms 1.1 api 
wasn't in Orbit...but now it is.  I've opened a piggy back CQ to consume 
it [2].

In any event...I will modify our feature to include javax.jms in our the 
JMS repo, but what I'm not clear on is what I have to do (if anything) 
to the buckminster meta-data to allow the build to pickup/use the Orbit 
javax.jms 1.1 API bundle...for both compile of 
org.eclipse.ecf.provider.jms and to include the javax.jms bundle in the 
ECF JMS provider repo.  Any help with this question is appreciated.  
I've just pushed a refactored version without the internal lib to github 
repo, and expect the build of the JMS feature to fail on our builder 
when I give it a run.

Thanks,

Scott

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=410237
[2] http://dev.eclipse.org/ipzilla/show_bug.cgi?id=7335