Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] EBR for MongoDB (RE: Updating org.eclipse.orbit.mongodb with the latest mongo java driver (3.2.6))

(cc'ed orbit-dev and ebr-dev to make them aware of the discussion)

Hi,

There are few things mixed up here.

Here are the rules:
1. no CQ is required for publishing receipts in EBR
2. one CQ is required for the new version of the library
3. another CQ is required for adding a new version of a library to Orbit

The name "org.eclipse.orbit.mongodb" was used because the MongoDB drive code had been modified for IP reasons in order to be distributed by Eclipse projects. Details are noted on the original CQ as well as in the CVS and in the jar itself. There should be a MODIFIED.txt file.

As long as that IP issue is still in place, any new version of the MongoDB driver must be patched again and again. The CQ should unveil any such IP issues.

If the modification is not longer required, the BSN should change from "org.eclipse.orbit.mongodb" to "com.mongodb" as per the Orbit naming conventions.

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).

So, if you want to update the library in Orbit, these are the steps that must be performed:
1. Create a CQ for the new version of the library.
2. Wait till it is approved (you can continue in case of parallel IP process)
3. Create a CQ for adding it to Orbit
4. Prepare the library for Orbit (using EBR and the advices given above)
5. Submit Gerrit review with the recipe to the Orbit Git repo.

-Gunnar


On 22 Jun 2016, at 11:20, Vidyadhara Reddy Vanga <vvanga@xxxxxxxxxxxx> wrote:

Hi Gunnar,
 
I have not got the CQ.
 
For test build I ran following command
 
mvn -U clean package -DdirtyWorkingTree=warning and I got below error message
 
-----------------
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.23.0:build-qualifier (default-build-qualifier) on project org.eclipse.mongod
b.ebr: Working tree is dirty.
[ERROR] git status recipes/unsorted/org.eclipse.mongodb.ebr_3.2.2:
[ERROR]
[ERROR] Untracked files:
[ERROR] recipes/unsorted/org.eclipse.mongodb.ebr_3.2.2/src/main/resources/about.html
[ERROR] recipes/unsorted/org.eclipse.mongodb.ebr_3.2.2/osgi.bnd
[ERROR] recipes/unsorted/org.eclipse.mongodb.ebr_3.2.2/src/main/resources/about_files/THE_APACHE_SOFTWARE_LICENSE__VERSION_2.0.txt
[ERROR] recipes/unsorted/org.eclipse.mongodb.ebr_3.2.2/.project
[ERROR] recipes/unsorted/org.eclipse.mongodb.ebr_3.2.2/pom.xml
[ERROR] recipes/unsorted/org.eclipse.mongodb.ebr_3.2.2/src/main/resources/OSGI-INF/l10n/bundle.properties
[ERROR]
[ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above).
[ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring
[ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
------------------
 
To proceed further I added recipes\unsorted to .gitignore file and build was successful.
Could you please let me know for information that you want to check.
 
Thanks & Regards,
Vidyadhar.
 





Back to the top