[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] building problem with JMS provider p2 repository

[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.lunifera.dependencies.p2 raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT
[ERROR] Missing requirement: org.lunifera.dependencies.feature.ecf.headless.feature.group 3.7.1 requires 'org.eclipse.ecf.provider.jms 0.0.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.lunifera.dependencies.p2 raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on: org.lunifera.dependencies.feature.ecf.headless.feature.group 0.0.0

As Markus already requested...it would be very helpful if we could see/try out the build that is generating this error. It seems from the above that the org.lunifera.dependenceis.feature.ecf.headless.feature group is not able to access a repo with org.eclipse.ecf.provider.jms plugin in it. The org.eclipse.ecf.provider.jms bundle is depended upon by the ActiveMQ provider. It's hard to know exactly why, just given this...but a few things to clarify:

1) the org.eclipse.ecf.provider.jms bundle is not in the ECF SDK repo...but is rather in a repo of it's own here [A]. Unfortunately we currently have to have these bundles in a repo separate from the ECF SDK repo...because of dependencies licensing (ActiveMQ). The bundles in the JMS feature do depend upon some of the bundles from the ECF SDK.

2) I (Scott) have been recently making cod changes (API addition/generalization) to the JMS/ActiveMQ provider...so that it can be used for implementing an MQTT provider [B]. I believe, however, that I am now (11/27) mostly done with the code changes to the JMS/ActiveMQ provider.

3) Even though done with code changes to the ActiveMQ provider...there is some feature restructuring that should/must take place to support the releng for the new MQTT provider [C]. I anticipate beginning this feature restructuring starting next week (Dec 2). If you have comments about how you would like to see features restructured to support your usage we will certainly try to accomodate you, so please add comments about your use case either on [C] and/or on [D]. We are particularly interested in better supporting non-Eclipse use cases of ECF Remote Services, and so would very much like your input about that before the restructuring effort begins. We will do as much as possible to meet your needs...within the limits imposed by licensing etc.

4) While working on 3...we can/will make the existing JMS repo available in a form that should be consumable by your build (e.g. p2 repo, maven, jar files). Just please let us know what the best form will be.



[A] http://build.ecf-project.org/repo/C-HEAD-jms.feature/lastSuccessful/archive/site.p2/
[B] https://bugs.eclipse.org/bugs/show_bug.cgi?id=420896
[C] https://bugs.eclipse.org/bugs/show_bug.cgi?id=422626
[D] https://bugs.eclipse.org/bugs/show_bug.cgi?id=409787

On 11/27/2013 12:21 PM, Markus Alexander Kuppe wrote:
On 11/27/2013 09:12 PM, "Cristiano Gavião" <cvgaviao@xxxxxxxxx>" wrote:
Worth to say that when I remove the jms feature and build my feature
with only ECF stuffs everything works properly.

any tips are welcome...
Is your build available somewhere to test it locally?

M. _______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ecf-dev