> I've also been asked to look at a better approach to target provisioning > prior to building. Today, we unpack an Eclipse SDK zip + any referenced > SDK/runtime/update zips, p2.director install from referenced update sites / > zips any required features, then start fetching sources and orbit bundles. > But requiring an SDK when you're running in Eclipse is not the best scenario > for RCP and equinox people, so we've started discussion here: > > > This is a good example of build overlap. There is also some discussion on PDE/Build about using a target definition file to provision your target before building:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=266311 I don't know if it makes sense for Athena to first provision your target (and then use the results of this as a baseRepoLocation / pluginPath), or if PDE/Build should support this internally. The fact that this conversation is spanning 3 lists shows a great deal of overlap between these technologies. cheers, ian -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource
_______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
