Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[orbit-dev] Trying out the EBR approach for adding XML RPC 3.1.3 to Orbit

Dear orbit-ers,

I've finally gotten around to starting the work to add Apach XML RPC 3.1.3 to Orbit.

This involves 3 jars, i.e. 3 bundles : commons, client and server.

I've tried to understand all the info about adding bundles from the wiki, and the info on the EBR-based approach on https://git.eclipse.org/c/orbit/orbit-recipes.git/tree/README.md

I would like to get feedback / guidance on the next steps, as this is a first-time Orbit contribution for me.


This is where I am at this moment :

1. created an ATO CQ https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11780 , PB on 5204. 5204 refers to the 3 components / jars, so I assume/hope 1 PB ATO CQ is sufficient as well?

2. created the recipes in my local clone from https://git.eclipse.org/r/orbit/orbit-recipes

3. tried the test builds per recipe
I had to disable the Tycho JGit build-qualifier stuff due to NPEs otherwise.
Cfr https://bugs.eclipse.org/bugs/show_bug.cgi?id=455007
The test builds then work fine.

Further questions :

4. Is it ok to put SNAPSHOT versions in the pom.xml for the added bundles, even when the original artifacts used are released versions? (this seems to be the default option in Orbit)

5. Do I need to wait for the ATO CQ approval before committing & pushing my new recipes to the Orbit git?
(As it's just recipes, not the external content itself...)


thanks a lot!


erwin




Back to the top