|
Hi Mickael,
A componentized build was our focus & goal when we started
this work.
Igor worked to understand the dependencies between software hosted
in various eclipse platform code repositories. He soon discovered
circular dependencies across/between code repositories that were
not practical to resolve without considerable effort. It became
clear that a monolithic build was necessary, at least in the short
term to complete the CBI platform build in a reasonable amount of
time & to enable LTS for Juno.
It is desirable to re-structure code in the platform code
repositories to resolve this and enable a componentized build.
What we need is a business driver to help encourage
organizations/people to pay for the work to be done.
Andrew
On 09/12/2012 11:28 AM, Mickael Istria wrote:
Hi all,
I'm sorry if I missed a debate or statement on this topic before,
but I'm wondering what is the planned grain for Platform build. As
it is currently documented, it appears that all projects in
Platforn need to be built simultanously, or sequentially on
the same Maven repo. This seems to be pretty monolithic, and
Maven/Tycho easily allows to separate build and tests for
projects, and to have Platform "Container" projects reusing those
builds to produce Platform artifacts (SDK, RCP...) and additional
testing.
Are there plans on (or arguments against) moving to a more
"composite" build?
|
