Perfect, thanks very much! The SimpleVariablePage code is pretty straightforward, it's exactly what I was looking for.
I'll update this thread as I make progress and/or get stuck (but it's a background thing for me, so it might not be very fast :). ᐧ Ned Twigg Lead Software Architect, DiffPlug LLC 949-264-3433 340 S Lemon Ave #3433, Walnut, CA 91789 On Fri, Nov 6, 2015 at 10:23 PM, Eike Stepper <[email protected]> wrote: > Hi Ned, > > That sounds interesting. I have no personal experience with Gradle, though. > > Ommph's plugins fall in three categories: > > 1) Model plugins (including .edit plugins), which should run fine outside > of OSGi. > 2) Core plugins, which are less likely to run outside of OSGi. They might, > but I haven't tried it. > 3) UI plugins, which certainly require OSGi. > > At this point we don't provide a headless installer application. In the > end installing boils down to creating, configuring, and starting a > SetupTaskPerformer instance. The two examples of that in our code (advanced > and simple mode) are in: > > org.eclipse.oomph.setup.ui.wizards.SetupWizardPage.createPerformer(SetupPrompter, > boolean) > > org.eclipse.oomph.setup.internal.installer.SimpleVariablePage.installPerform() > > Does that give you the needed start pointers? > > Cheers > /Eike > > ---- > http://www.esc-net.de > http://thegordian.blogspot.com > http://twitter.com/eikestepper > > > > Am 06.11.2015 um 22:47 schrieb Ned Twigg: > >> Hello there! I'm a big fan of Oomph, and of Gradle. I have started a >> project called Goomph <https://github.com/diffplug/goomph> on GitHub >> which tries to combine these things. >> >> Gradle already has the ability to make an eclipse project by adding a >> small snippet to your file. I'd like to allow users to add a little >> snippet that creates an Eclipse instance and workspace for them, using >> Goomph. Hopefully it could also use the Oomph bundle pool to create a >> target platform and help with dependency management. Clone a project, run >> `gradlew goomphStartIde` and you've got an Eclipse instance with all the >> plugins, projects, target platform, yada yada. >> >> This isn't an urgent priority for me, but it's something I'd like to work >> on in the background. I've got a couple questions: >> >> So let's say I've got a model in Gradle that has these things: >> >> 1) The update sites which contain the Eclipse installation and plugins >> that I need >> 2) The features that I want "org.eclipse.jdt, org.eclipse.rcp, >> org.eclipse.pde" >> 3) A directory where I would like the Eclipse launcher to be installed >> >> How can I pass these to Oomph and then monitor its progress? Can I use >> the Oomph jars to create an EMF model, save it to disk, and then pass that >> as a command-line arg to the Eclipse installer runtime? >> >> Is it possible to use the Oomph jars outside of an OSGi environment at >> all? >> >> Anyway, just looking for pointers for how I should get started. >> >> Thanks! >> >> Ned Twigg >> Lead Software Architect, DiffPlug LLC >> 949-264-3433 >> 340 S Lemon Ave #3433, Walnut, CA 91789 >> ᐧ >> >> >> > > _______________________________________________ > oomph-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/oomph-dev
_______________________________________________ oomph-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/oomph-dev
