Eclipse Community Forums: Oomph » Testing changes in project setup files

Home » Eclipse Projects » Oomph » Testing changes in project setup files

Testing changes in project setup files [message #1816440]

Tue, 29 October 2019 09:59

Eclipse User

I'm would like to test changes in a project setup file for Dartboard.

Here is what I think should work:

1.) Select "Eclipse IDE for Eclipse commmiters" on the first page of the advanced setup wizard
2.) Switch to second page
3.) If I see an existing Dartboard entry, select it and use the Delete button in the toolbar to remove it
4.) Drag and drop the project file on the correct position in the tree avoiding https://bugs.eclipse.org/bugs/show_bug.cgi?id=552315, this creates an new Dartboard entry
5.) Press next
6.) In the following Variables view I tried an existing entry and a new one (both did not work)
7.) Switch to the next page and press Finish

The Confirmation page shows me only a subset of the task and after running it, I end up with an empty WS.

I'm reset all my changes to the file contributed by Ed but I still end up with an empty WS.

What is wrong with the above procedure? IIRC the first time I did this, it worked fine. I created a animated Gif to show what I'm doing.

index.php/fa/36670/0/

Attachment: oomph.gif
(Size: 4.36MB, Downloaded 517 times)

Re: Testing changes in project setup files [message #1816452 is a reply to message #1816440]

Tue, 29 October 2019 11:48

Eclipse User

Btw, this seems also the testing procedure described here: https://wiki.eclipse.org/Eclipse_Oomph_Authoring#Testing_the_Setup_Model

Re: Testing changes in project setup files [message #1816455 is a reply to message #1816452]

Tue, 29 October 2019 12:04

Eclipse User

Your video is awfully fast. Did you actually check the project or did you only select it? I suspect the latter. Read the instructions at the top of the wizard page. If in doubt, click the spinning help button (designed to attract your attention) and read those things too.

And note that the setup is designed to be testable in the running IDE itself. I.e., the Eclipse Ini task is designed to locally redirect your running IDE to use the workspace version of the setup. So that's often the easiest/fastest way to test.

Re: Testing changes in project setup files [message #1816458 is a reply to message #1816455]

Tue, 29 October 2019 12:12

Eclipse User

> Did you actually check the project or did you only select it?

Silly me, sorry. Setup now executes correctly.

>And note that the setup is designed to be testable in the running IDE itself. I.e., the Eclipse Ini task is designed to locally redirect your running IDE to use the workspace version of the setup. So that's often the easiest/fastest way to test.

I don't get this. I have the Dartboard.setup file in my IDE. How can I test it now without starting a new installer? Or this is for the new IDE, describes on the wiki as: "Then start the setup process from within this IDE via the main menu, Help → Update.png Perform Setup Tasks.... This "manual trigger" will pop up a confirmation dialog before starting the setup process so that you can review what tasks are scheduled for execution."

Re: Testing changes in project setup files [message #1816468 is a reply to message #1816458]

Tue, 29 October 2019 14:16

Eclipse User

Ed means this: if you drag the link https://raw.githubusercontent.com/eclipse/dartboard/master/org.eclipse.dartboard.releng/Dartboard.setup into the installers second page ("Projects"), the installer will create a workspace with that remote URI linked into it. If you then try to open the setup editor on it, e.g. via the Open Setup drop down menu of the Oomph toolbar, the file will be in read-only mode because it's an https URI. With the EclipseIniTask he added to your setup (see https://github.com/eclipse/dartboard/blob/master/org.eclipse.dartboard.releng/Dartboard.setup#L142 ) this https URI is redirected to the file URI within your local Git clone (which has been created by Oomph at this point). So opening the Setup editor allows you to edit and save the file back to your clone.

Re: Testing changes in project setup files [message #1816484 is a reply to message #1816468]

Tue, 29 October 2019 23:34

Eclipse User

Yes, so using Navigate -> Open Setup -> <your-project-stream> , which always opens your project's setup, because of the redirection, that setup is in fact (and will open) the file in the clone, which is also typically a file in your workspace. That's also the version used by Help -> Perform Setup Tasks... so you can make changes locally and perform them in the already-running IDE. Note too that the Perform wizard that comes generally starts on the Confirmation page, but you can go back to the Variables page and use the "Show all variables" check mark to see all the variables and even change them, e.g., to change the target platform choice.

When authoring setups it's a good idea to turn on Live Validation (on the menu) if it's not already turned on and it's good to consider what is being displayed in the outline because here you can see other types of errors you might make, e.g., using a variable name without having defined the variable itself. Also, in the "Unresolved Variables" section you will see all the variables that will be prompted for a value from the user (and for any variable you can see all the places where that variable is used in other setup tasks). The Outline is kind of a preview of what you will see in the wizards when using this setup.

Re: Testing changes in project setup files [message #1816505 is a reply to message #1816484]

Wed, 30 October 2019 05:50

Eclipse User

Thanks Ed and Eike. That works and testing a setup profile is much nicer this way. Thanks a bunch.

Re: Testing changes in project setup files [message #1858206 is a reply to message #1816505]

Thu, 23 March 2023 01:05

Eclipse User

How does this procedure work when you are testing a Configuration? I have followed the instructions, but the setup from within does not recognize the changes in the config model. I guess this makes sense, as it references the information provided by the product.

Re: Testing changes in project setup files [message #1858210 is a reply to message #1858206]

Thu, 23 March 2023 03:26

Eclipse User

I'm not sure exactly what resources are all involved in your question...

In general, if you want to test changes locally for resources changed locally, but the references to those resources are remote (e.g., in a git clone), you will need a redirection from the remote URI to the local URI. That's why most project setups include a task similar to this:

<?xml version="1.0" encoding="UTF-8"?>
<setup:EclipseIniTask
    xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
    option="-Doomph.redirection.setups"
    value="=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->${git.clone.oomph.location|uri}/setups/"
    vm="true">
  <description>Redirect to the development version of the releng setup model.</description>
</setup:EclipseIniTask>

Then the eclipse.ini will contain

-Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/
-Duser.home=D:\Users\merks

In this case it's a folder redireciton (both end with /).

Any system property that starts with oomph.redirection. will be added to the URIMap for this purpose. If you want this in the installer, you can run it with

<eclipse-inst-executable> -vmargs -Doomph.redirection.foo=https://...->file:/...

If you want to test like for a new user, you can use use

-Duser.home=<folder-you-can-delete-later> -Doomph.setup.user.home.redirect=true

to specify where the home folder is located and to specify that the installation itself should also contain the same -Duser.home=... in the eclipse.ini.

Previous Topic:	'Perform Setup Tasks..' P2 task doing more than I'd expect
Next Topic:	oomph advance mode

Goto Forum:

-=] Back to Top [=-

Current Time: Sat May 17 09:13:29 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter