Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Oomph issues
Hi, Ernesto,

More replies, below.

Thanks for helping with this discussion!

cW


On Jul 23, 2014, at 1:35 PM, Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:

Thanks Christian. My replies are below.


On Wed, Jul 23, 2014 at 12:15 PM, Christian W. Damus <give.a.damus@xxxxxxxxx> wrote:
Hi, Ernesto,

See some replies in-line, below.

HTH,

Christian


On Jul 23, 2014, at 12:02 PM, Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:

Hi. I've been trying to use Oomph to setup a development environment and I've run into several issues. After several attempts I finally got a working environment, but every time I restart the IDE, the Oomph dialog pops up with a new subtask that resets the default JRE back to 1.6 (I had set it to 1.7 as the drop-down list showed only 1.7 and 1.8; and by the way, the drop-down list for 1.7 shows only 1.8 even though I don't have it in my machine):

The way that Oomph deals with JREs is perhaps not entirely intuitive.  The core model that all setups inherit lets any particular JRE be re-directed to an instance of a later (higher-version) JRE, because a later JRE is compatible with an earlier.  The reverse is not true, so for example, Oomph doesn't let you re-direct a 1.6 JRE to a 1.5 instance.  This is why the drop-down only shows higher versions.

As you noticed, if you select one of those drop-down versions, then Oomph will require a value for that, either redirection to yet another later JRE or an actual location on your system.

The baseline for Papyrus Luna is 1.6, which is why the setup model starts with that.

Once you have provisioned an actual JRE install, Oomph shouldn't be prompting for JREs again (at least, not for the same Papyrus setup).  If it does, that's a bug that should be reported to the Oomph team.


[11:39:56] Performing setup task JRE JavaSE-1.6 = /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/bin

[11:39:56] Configurating a JavaSE-1.6 JRE for location /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/bin


This all looks correct.

I figured out part of the problem: I had set the JRE path to include the final /bin. 

When I edit that in Preferences>Java>Installed JRE to remove the /bin, the errors go away, but on the next restart, it goes back to the path with /bin.

Ah, OK, right.  That makes sense.  Perhaps there might be some validation that could be added to the Oomph variable editor for JREs ...  Might be worth an enhancement request to the Oomph team.



The actual value for 1.6 does point to 1.7.0_51, as I told the Oomph installer, but I get the errors anyway, so I have to manually go back to Preferences>Java>Installed JREs and set it back.

I haven't seen this.  I configured my own Papyrus setup to use a 1.7.0 JRE for 1.6 as you did, and it's working fine.  I don't have to tweak any settings.  What do you mean by errors?  Entries in the Error Log?  

These are errors on the imported Java projects. The error entries in the "Problems" view are that the build path is incomplete, and that some types (including java.lang.Object) cannot be resolved. See the attached screenshot.

Right, again that makes sense.  Without a JRE, the Java SDK libraries are absent.



What specifically is the JRE preference set to and what specifically do you set it back to?  (sorry, I'm having trouble visualizing what you're actually seeing)

See the second screenshot: I have several JREs installed. The default is "JRE for JavaSE 1.6" set to the path above with /bin. I've tried two things:

1 - changing the default to Java SE 7
2 - keeping the 1.6 default and editing its entry to remove the /bin

Both alternatives resolve the build path issue, but on restart, Oomph resets the default to 1.6 with the location ending in /bin. It seems to me that on start up Oomph detects if there where changes to these preferences and resets them to the values given to the installer. Is this what happens? The problem then is what if those values were wrong in the first place.

Right.  On start-up, Oomph does what it can to make sure that your workspace is configured as specified by the start-up model that it references.

You need to change the value of the JRE 1.6 variable that you entered into the installer.  To do that, hit the "Perform Setup Tasks..." toolbar button (the yellow and green arrows in a circular formation) and select the "Show all variables" checkbox in the first page of the wizard.  This lets you edit variables that the installer had saved the first time.



Should I have manually set the variable for JRE 1.6 instead of selecting from the drop-down when installing? or is there a way to avoid having Oomph reset it every time?

I also encountered other problems: 

* when setting up Gerrit, my password is not accepted and the only way to continue is to click "Cancel".

Is it the correct Gerrit password?  Are you an Eclipse committer?  If not, you won't have a Gerrit account and you'll have to use one of the anonymous options supplied by Oomph.

I am not an Eclipse committer, but I do have an account at dev.eclipse.org, and did open a Gerrit account (at https://git.eclipse.org/r). I understand that the password to use is the one automatically generated under "Settings>HTTP Password", right?

Sorry, I don't know what that generated password is.  I am an Eclipse committer, so I didn't have to do any Gerrit account set-up.  Whatever credentials work in EGit to connect you to a Gerrit repository should work also in Oomph.  If not, I'd suggest you ask the Oomph team for help on the eclipse.tools.oomph newsgroup.


I missed the anonymous options in Oomph. Do you mean just to leave the "Eclipse ID user" blank?

One of several options for the Git repository URL is "HTTPS (read-only, anonymous, Gerrit)".  You should see that in the "Papyrus Git or Gerrit Repository" variable (you may need to check the "Show all variables" box in the Oomph installer).



* when installing the Developer package + UML-RT, I got a couple of missing dependencies:
    - org.eclipse.acceleo.*
    - org.eclipse.gmf.codegen.xtend.*
    - all of umlrt (although when I installed only UML-RT it did work)

Please raise a bug on Papyrus for this, with details of how to reproduce the erroneous set-up.  Thanks!

I'll do that.
 

* if I don't close the initial (bootstrapping) dialog, the second one (startup) blocks at some point. It unblocks once you hit "Finish" on the first one, but since there's no hint that you have to do that, I thought that the start-up was working for a very long time.

This should be reported to the Oomph team in bugzilla.  It's a normal consequence of stacking dialogs with modal behaviour, but it's not a great experience.

I'll report it as well.
 
Thanks




Thanks!


--
Ernesto Posse

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev



--
Ernesto Posse

<Screenshot 2014-07-23 12.55.04.png><Screenshot 2014-07-23 12.57.11.png>_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

Back to the top