Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » How do I develop/debug an oomph setup Task
How do I develop/debug an oomph setup Task [message #1798630] Wed, 21 November 2018 11:54 Go to next message
Peter Lamby is currently offline Peter LambyFriend
Messages: 4
Registered: November 2018
Junior Member
There is a feature I want to see in the "Maven Import" Task. I reported and now I am trying to develop a patch for this feature.

You can find my attempt at

But I don't found any documentation on how to use the new org.eclipse.oomph.setup.maven artifact (I bumped the version number)

How can I launch a new eclipse installation with a .setup file, the new artifact and debug eclipse?
Do you have any documentation/pointers for me?
Re: How do I develop/debug an oomph setup Task [message #1798635 is a reply to message #1798630] Wed, 21 November 2018 12:44 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 30882
Registered: July 2009
Senior Member
Peter, if you're trying to enhance MavenImportTask, it would seem best that you provision the same development environment we use for Oomph:

With your Eclipse account you will be able to commit changes to Gerrit for review. Be sure to choose a read/write Gerrit URI for cloning the repository. This process makes it very easy for us to track, review, and accept your changes.

For this change, I imagine you need to modify the Ecore model /org.eclipse.oomph.setup.maven/model/Maven.ecore to add some additional attribute to the model. Then open the *.genmodel to regenerate the code. Then finally in MavenTaskImportImpl you'd add whatever logic is needed to set the profile(s) using during import.

The setup includes launchers to launch the installer, to launch a runtime workspace and even one to locally do a Maven build (which is useful if you launch the installer so that it installs your locally build updated versions of Oomph). You can remote debug the launched installation too, but it is easier to debug things in a runtime workspace. You can always use Navigate -> Open Setup -> Workspace to create task that will perform in the runtime workspace so you can follow the logic in the debugger...
Previous Topic:setup for project using Bndtools and a Bnd Workspace
Next Topic: site is not stable.
Goto Forum:

Current Time: Mon Feb 17 18:47:30 GMT 2020

Powered by FUDForum. Page generated in 0.14667 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top