[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Criteria for Platform team to use CBI

On Fri, Mar 16, 2012 at 8:39 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
David,

Can you clarify if use of map files is a requirement by itself or the
goal here is to have reproducible build and mapfiles is one possible way
to achieve this goal?



This is Kim's list from early on in the CBI process. There's no reason why this can't still be discussed, but I was under the impression that the requirement going forward was "reproducible build and mapfiles is one possible way to achieve this goal". Based on the CBI discussions it probably is not the way forward when using maven+tycho.

The map files serve 3 purposes:

1) control the build input
2) determine where the plugins are that need to be built
3) control the qualifiers generated.

In the CBI prototype, #1 is provided by the aggregate repo itself, #2 is provided by the aggregate repo + pom.xml hierarchy, and #3 is https://bugs.eclipse.org/bugs/show_bug.cgi?id=370707

The more interesting problem was how to build maintenance branches on previous releases, like 3.7.2+ and 3.6.2+, where the build is map file controlled, but at least last time this was out of scope for the CBI prototype. This is https://bugs.eclipse.org/bugs/show_bug.cgi?id=367581 I think.

Later,
PW

--
Paul Webster
Hi floor. Make me a sammich! - GIR