Hi, Andrew,
I'm not really sure why it failed, but I think it was the settings that I was using. When I gave up on making my own
changes and tried exactly as in your video it worked. I'm not sure if it was a coincidence or if the settings really
were causing problems.
Hmmm ... it's supposed to be so easy that a video tutorial is not required. :-/
I was trying to change things like the location of the bundle pool, using absolute paths for installation, workspace,
git checkout, and a few others.
One error that was unrelated to the settings (I think) was a "Too many files open" exception after running for awhile.
Restarting the installer and trying again got past that problem. I think this might be a bug in Oomph, but I'm not able
to reproduce it anymore so it is tough to say.
Yeah, that would be an Oomph bug. There shouldn't be any way to devise a setup model that causes this.
Another thing that I just remembered -- after installing (using a Java6 VM), it refused to load because the IDE requires
Java7. I can see that requirement in the generated eclipse.ini file -- could it have come from the papyrus.setup model?
I was able to get past the problem by switching to a Java7 VM. However, AFAIK, Papyrus is still supposed to work on Java6.
Indeed, I see now in my own Oomph-built Papyrus IDE install that there are two occurrences of
-Dosgi.requiredJavaVersion=1.7
and one occurrence of
-Dosgi.requiredJavaVersion=1.6
in the Eclipse.ini. I have no idea where these come from because there is no reference to this property in neither the Papyrus Oomph model, nor the product install model that it inherits, nor in the Oomph source code. And, oddly, the 1.6 requirement is the last specified in the Eclipse.ini, so I would assume that it's the one that would actually have effect (how does it look in your Eclipse.ini?). In any case, it's not so bad if the development workbench requires 1.7, as long as it supports running and debugging Papyrus with a 1.6 VM, which it does just fine.
But, thanks for sending me on a search of the papyrus.setup, because I found preference settings in there for VM installations specific to my Mac. Oops.
cW
|
