Re: [cross-project-issues-dev] Indigo aggregation builds are open for bu

[Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>]

Thanks, Daniel, for the pointers.

From your links and my first experiments I drafted a wiki page:
  http://wiki.eclipse.org/Indigo/Contributing_to_Indigo_Build

It'd be great if someone qualified checks for any mistakes and
adds missing info.

thanks,
Stephan


On Monday, August 23, 2010 03:30:32 pm Daniel Pastore wrote:
> Hi Stephan,
> 
> On Sun, Aug 22, 2010 at 12:35, Stephan Herrmann <stephan@xxxxx-
berlin.de>wrote:
> > Hi David,
> > 
> > On Wednesday, August 11, 2010 07:59:52 am David M Williams wrote:
> > > For anyone "new" (joining Indigo, but wasn't in Helios) you are welcome
> > 
> > to
> > 
> > > give it a try now if you'd like, but might take some "back and forth"
> > 
> > here
> > 
> > > on the list to get you going. Feel free to ask any question, as I
> > > forget what's common knowledge, and what's not.
> > 
> > I'm currently preparing the Object Teams Project for joining Indigo.
> > However, the switch to the b3 aggregator leaves me without a simple
> > howto for creating a contribution file. Note that
> > 
> >  http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan
> > 
> > still points to  (look for "Contributing to Indigo Build"!):
> >  http://wiki.eclipse.org/Helios/Contributing_to_Helios_Build
> > 
> > where a nice example with explanation is given. Yet, it appears to
> > be an out-dated model.
> 
> For Sequoyah, our .build file was migrated to .b3aggrcon file, and their
> structure is very similar, so our changes were minimal.
> You could begin with any of these files, since the conversion from the old
> format to the new one is pretty straightforward.
> You can check our files if you want. :)
> 
> Is an updated howto on it's way? What's the recommended way -
> 
> > preferably without requiring me to read tons of b3 documentation :)
> 
> David Williams has already mentioned some benefits and improvements from
> this new file at
> http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg04575.html
> (and
> a little bit more at https://bugs.eclipse.org/bugs/show_bug.cgi?id=312645).
> We've read it, and it makes sense for us. :)