Yeah, I've been thinking that I need to define a product for my (overall) project, but I've been avoiding it. I don't actually think of it as a product but I guess that's the only way to package it, short of manually building Eclipse IDE instances for each platform. :O
This is getting OT for list, but anyone have ideas about what the simplest approaches are using existing tools? Obviously I'd prefer fully automated but I can live with some manual steps. 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
