Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGt6o8=5OdbUc+rZL-WvjGcuMZM3whQ2mgLFPAYsOipopwgwVA@mail.gmail.com>
References: 
 <CAGt6o8kL8k6R==V4yMWD6YTAN6yP64VL5JZjwzLytxDERoTUCw@mail.gmail.com>
 <CAKoNANuyeHjMGzTgnzB1EROAX+CPeVg2T-zwatXOL7qrLoFYKA@mail.gmail.com>
 <CAGt6o8=5OdbUc+rZL-WvjGcuMZM3whQ2mgLFPAYsOipopwgwVA@mail.gmail.com>
From: Raul Kripalani <raulk@apache.org>
Date: Sat, 22 Aug 2015 13:28:58 +0100
Message-ID: 
 <CAKoNANuowS8wVTK4F17kiLnS49+F+aXtmBybBsNGAP2pg4NUVA@mail.gmail.com>
Subject: Re: New module for C++/.Net integration.
To: dev@ignite.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c3f386806267051de588c7

--001a11c3f386806267051de588c7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 21, 2015 at 4:47 PM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> 1) We have 4 distinct parts: Java supporting code, common CPP/JNI layer
> which depends on Java, .Net implementation which depends on Java and JNI,
> CPP platform implementation which depends on Java and JNI. And very often
> it is necessary to update several of  them in scope of a single ticket. I=
t
> will be a nightmare to update them in different repos - tons of patches
> and/or pull requests.
>

I see what you mean; if I understood, it's a matter of (1) convenience and
(2) being able to push commits that contain all changes to support a given
functionality across all platforms.

Have you considered Git Subtrees? With that approach I think you can get
the best of both worlds (separation in different Git repos, and mapping of
"satellite" repos into directories of a core repo). In my mind, we would be
having 3 repos:

* Repo "ignite" =3D> Ignite (Java) + CPP/JNI layer. This is essentially
Ignite + the contract and interop layer for other languages to leverage
Ignite.
* Repo "ignite-cpp" =3D> platform implementation for Ignite in C++.
* Repo "ignite-dotnet" =3D>  platform implementation for .NET.

The ignite repo would map the ignite-cpp and ignite-dotnet repos into the
source tree via git subtree.

Considerations:

* Folks only wanting to interact only with ignite's Java code would not
need to fetch the ignite-cpp and ignite-dotnet repos. Most people will fall
in this category, I assume.
* Git subtree automatically takes care of splitting commits that span
multiple repos, for them to be applied individually to each repo.
* Tagging commits with JIRA ticket ids allow us to group commits across a
number of repos under the "umbrella" of a single functionality.

For those people who are not familiar with Git subtrees, this is a nice
walkthrough: [1].

[1] https://medium.com/@v/git-subtrees-a-tutorial-6ff568381844

*Ra=C3=BAl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

--001a11c3f386806267051de588c7--