Community
Participate
Working Groups
The new mqtt provider ( bug 420896 ) does not have an associated feature. To make this possible, a new set of JMS features should be created so that only the JMS API is available in a new feature...and the ActiveMQ provider and the MQTT provider can then include that feature.
There is now an MQTT provider build running that - although marked failed - produces a p2 repo [1]. The reason its failing is because the test cannot be run yet. This is due to two reasons: - The test bundle is missing a .launch file (please see e.g. JMS repo as a blueprint) - The MQTT test bundle depends on the JMS test bundle but we do not publish test bundles*. [1] http://download.ecf-project.org/repo/C-HEAD-jms-mqtt.feature/builds/lastUnsuccessfulBuild/archive/site.p2/ *The more I think about it, I come to believe that Eclipse features are not the way forward (they tend to never fit the bill). I would rather like to see us publish built bundles to some (simple) file repository and/or use OSGi's newly spec'ed features. Eclipse features could then be generated on the fly for backward compatibility.
FTR: The test bundle is commented out in /org.eclipse.ecf.provider.jms.mqtt.feature/buckminster.cspex
(In reply to Markus Kuppe from comment #1) > There is now an MQTT provider build running that - although marked failed - > produces a p2 repo [1]. > > The reason its failing is because the test cannot be run yet. This is due to > two reasons: > > - The test bundle is missing a .launch file (please see e.g. JMS repo as a > blueprint) I've created a test bundle launch config and added in the project directory for org.eclipse.ecf.tests.provider.jms.mqtt project. > - The MQTT test bundle depends on the JMS test bundle but we do not publish > test bundles*. I'm soon going to begin refactoring of ECF features...and part of that will be refactoring JMS features.
