Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [soa-pmc] build system

Hi Chris

Here is the preparatory and final notes of the telco by Adrian.

Basically, Oisin advises to use the B3 Aggregator to aggregate P2 sites produced by individual project builds, which in turn may use any build system. And Oisin can provide some help, at least to Engineering which unsuccessfully tried PDE and is now interested in using Buckminster.


Christian Saad a écrit :
Hi Adrian, Marc,

unfortunately I wasn't able to join the call today. Did you decide on how the subprojects will be aggregated into the SOA build?


Am 13.09.2010 16:38, schrieb Christian Saad:
Hi all,

unfortunately I wasn't able to join the call today. Did you decide on
how the subprojects will be aggregated into the SOA build?

--- Begin Message ---
Hi Oisin,

great, skype sounds good. 
Regarding the requirements, from Mangrove point of view, they are rather basic:
- headless build system for the Mangrove code base (split in various modules)
- generation of the various Mangrove features
- integration of the result into the overall SOA TLP releases

If I understood correctly, buckminster can be use for the Magrove build (with the different modules) and the generation of the features, while b3 can be used in the overall SOA TLP build to aggregate the various projects.

So on my side, what I'll like to know is what kind of structure I need to have in Mangrove (different directories and so on) to make [re]using as much of your Buckminster code easy. And then of course how all this can be put into b3.

For people that do not want to use Buckminster within their project, I imagine they will only be interested in using b3?

Talk to you in a few minutes.

On Sep 13, 2010, at 8:44 AM, Oisin Hurley wrote:

>> I have booked a phone line (+33 1 72 12 29 69) but perhaps skype is also an option (my ID is domnueipi).
> Let's try doing the skype conference approach shall we? It would be a good
> idea to put a bit of structure on this - with no confirmation mail for
> a time, I
> haven't prepared any starting point code - so let's do a survey of what's in
> the overall container project, what requirements each project has and get
> those down for the record.
> --oh

soa-pmc mailing list

--- End Message ---
--- Begin Message ---
  • From: Marc Dutoo <marc.dutoo@xxxxxxxxxxx>
  • Date: Mon, 13 Sep 2010 18:40:10 +0200
  • User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv: Gecko/20100802 Thunderbird/3.1.2
 Hi Adrian, all

Just to mention again that JWT has now a working Athena/CBI build and some knowledge and resources about it : , in addition to the helpful dash-dev mailing list (ex. ).


Le 13/09/2010 10:52, Adrian Mos a écrit :
Hi guys,

here are the notes from today. I will contact Lynn for an Adobe Connect room tomorrow and keep you updated


- we must aggregate individual P2 sites as in Helios
- we need an overall container project
- used to build everything from source (we don't want to do the same here)
- we want people to manage their own releases for their individual projects
- the container project will point to the individual P2 sites

- what build system for individual projects? (PDE build, Buckminster, Athena etc?)
- PDE Build is very basic - a framework for generating Ant scripts
- Athena is PDE with some wrappers around to hide some complexity
- Buckminster delegates to an internal PDE build

Oisin recommends Buckminster: He had trouble with PDE build. And moved to Buckminster, which is easier.

Projects that need their own individual build (ask on the dev-list):
- Mangrove (wants Buckminster)
- eBPM (PDE Build, maybe moves to Buckminster)
- eBAM (nothing, maybe moves to  Buckminster)
- Swordfish (PDE Build?)
- JWT (Athena?)

--- End Message ---

Back to the top