Thanks Gunnar. We will use "com.mongodb.ebr" then.
We have a another question:
- If we create a EBR bundle, can we ship it with our BIRT Designer? Currently we ship our Orbit bundle for MongoDB 2.6 (org.eclipse.orbit.mongodb) with
our BIRT Designer. The line in red below seems to be saying that we cannot bundle the EBR with BIRT Designer (which is an Eclipse project). Can you clarify / confirm? Or let me know if I misunderstood the statement.
For EBR, the namespace "org.eclipse" must not be used. Instead, you should use "com.mongodb.ebr". As a side note, EBR also does not address any IP issues. There is no IP review of any library. Just the recipes need to be IP clean (contributed
properly). It must be clear that a bundle created from a recipe cannot be distributed by an Eclipse project. A full IP review is required (see rule #2 above).
thanks,
Derek
From: ebr-dev-bounces@xxxxxxxxxxx [mailto:ebr-dev-bounces@xxxxxxxxxxx]
On Behalf Of Gunnar Wagenknecht
Sent: Wednesday, July 13, 2016 12:27 AM
To: Discussion channel for EBR developers and recipe contributors
Subject: Re: [ebr-dev] Question on creating EBR for MongoDB 3.x java driver
Hi Derek,
I would like to get confirmation on whether this is the right approach. Or if going through the org.eclipse.orbit.mongodb route is a better approach, please let me know
too.
Just to clarify, you cannot use the "org.eclipse.orbit" namespace for anything in EBR. If your intention is to contribute this as an EBR recipe, please use "com.mongodb.ebr". If your intention is to contribute this to Orbit, please open
a Bugzilla and let's discuss this via orbit-dev. We might need to bring this to cross-project discussion as well (for awareness).
