| Re: [ebr-dev] Question on creating EBR for MongoDB 3.x java driver |
|
Gunnar, >> Such a bundle must be build within the BIRT project. We do not build it as part of the EBR project. I discussed with the folks in the BIRT project. Currently the way open source BIRT works is that it has to use external repository to download 3p libraries
like eclipse, GEF, EMF and EBR. That means EBR project must have a public repository URL to contain the build, so that other projects can download. If not, it cannot add to open source BIRT. Do you see what options we can pursue?
If EBR is not feasible, we may have to revert to the Orbit approach. But then MongoDB Orbit bundle is tied to an older version of MongoDB (2.6) right now.
Upgrading this entire bundle to use MongoDB 3.2 may cause problems for existing users who depends on Orbit MongoDB, I am afraid. Any suggestions? Comments? thanks, Derek From: ebr-dev-bounces@xxxxxxxxxxx [mailto:ebr-dev-bounces@xxxxxxxxxxx]
On Behalf Of Gunnar Wagenknecht Hi Derek,
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. The goal of EBR is to provide infrastructure and recipes for building bundles. To answer your questions, yes it MAY be possible to build and ship and EBR bundle from within the BIRT project. Such a bundle must be build within the BIRT project.
We do not build it as part of the EBR project. The BIRT project must have an approved CQ for the library. I currently don't see such a CQ for the BIRT project in IPzilla. Please engage with your PMC if the process in unclear. -Gunnar |