Thanks Dave. I definetly don't want to go the buckminster route as it looks 
like setting up a whole new build design and athena is working so well now!

The use case is  basically just giving the user exactly waht they would get if 
they downloaded the platform sdk and then went to my update sites. As much 
progress as P2 has made, some users are simply not going to get past the 
"download and then.." stage. I don't actually need a full product build, though 
I could do that if necessary. What I want is simply a downloadable SDK that 
includes the set of features I want. It seems like it should be theoretically 
easy to set this up, as there is already a perfect source update site built. 
I'm thinking that the basic steps are something like:

1. Grab donor SDKs for each of the respective platform builds and unzip them.
2. (The hard part) somehow trigger an automated install for each of those on 
the non-target machine.
3. Then zip everything back up and upload to download server.

I suppose one could just throw everything into dropins, but that would be a 
pretty ugly solution. Anyway, I could put together a simple ant script for this 
if I knew how to do step 2..anyone have any ideas?


On Dec 23, 2009, at 8:05 AM, David Carver wrote:

> Actually, what you want to do is a product build. Currently Athena is 
> structured only for feature based builds. While a product build is a feature 
> build on steroids, it has it's own complications that can occur. Initially I 
> think this is out of the scope of Athena, but is definitely in scope for 
> projects like Buckminster.
> 
> Dave
> 
> Miles Parker wrote:
>> Hi all,
>> 
>> I'm wondering if anyone has given thought to how difficult it might be to do 
>> full IDE cross-platform builds using Athena (prob. not actually on Athena 
>> Hudson given resource constraints) and/or other releng tools? I'm thinking 
>> that it makes the most sense to do this in two stages, i.e. build the zips 
>> using normal hudson build, and then package that into IDE builds somehow. 
>> Pardon the ignorance, but the release infrastructure is a little opaque to 
>> me. I suppose I could use the RCP tools for a local 
>> build..(http://wiki.eclipse.org/Building) but I wonder if there isn't a 
>> fairly OOTB automated solution out there..
>> 
>> cheers,
>> 
>> Miles_______________________________________________
>> dash-dev mailing list
>> dash-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/dash-dev
>> 
>>  
> 
> _______________________________________________
> dash-dev mailing list
> dash-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/dash-dev

_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev

Reply via email to