| Thanks Patrick.
Comments inline.
Sorry,
totally forgot the worst point discovered this morning:
Eclipse Oomph installations doesn't start anymore after a first
usage, while Luna 4.4M6 'fresh & clean' runs fine.
See attachement, does maybe someone know whats going wrong? No
further error log in the installation directory.
No idea. Did you move/rename something? This usually should not happen. I’d like to encourage you to open a bug report and tracking this one down with the committers of Oomph.
Best regards,
Patrick
Am 27.03.2014 14:15, schrieb Patrick
Gottschaemmer:
Hi Marcel,
finally I've had the time to test OOMPH, here are my results:
Fresh OS Installation / no SSH server keys stored (which was
luckily the case):
A UnknownHostKey SSH error occurs (see unknownSshHost.log
attached). Actually no big surprise, seems like OOMPH can't handle
this.
This *could* be noteworthy for new CoRe developers, as they
shouldn't have the Eclipse host SSH key.
This has been reported and according to Eike this will be fixed:
'demo-master' selection from the OOMPH installer menu:
Auth failure for the org.eclipse.recommenders.examples.git
repository (see demoMasterFail.log attached)
Probably my fault. I may have used something in the config that causes this.
Several crashes during installation
I've needed 3 attempts until Oomph went through the
installation without any critical crashes.
Unfortunately, Oomph didn't provide me any error logs, it just
froze.
Maybe it only looked like? I know that it takes a while sometimes. Especially when it sets the target platform. I filed a bug about it:
Besides these, I had no critical errors after installing the oomph
distribution (setting the target platform for recommenders
'master' in the first way crashed, but that could have been a
connection failure by me)
Really caused by you? If so, a click on the Refresh button from inside Eclipse would have fixed that. Did you use/know/find it?
However, for me Oomph isn't an suitable alternative to a
'classical' Eclipse setup due to the following reasons:
- Long installation time:
When downloading the bundles, Oomph creeped forward with
something about 200 KB/s, internet connection and Eclipse
servers went fine when downloading manually.
That sounds weird since it uses the same code as Eclipse and also recognizes mirrors. I pointed Eike to this thread. Maybe he has an idea. -
Sadly, you can't leave it alone since it needs some 'Accept
here!' and 'Click there!' moments, ofc.
Actually, you don’t have to press the ok button after the IDE provisioning. It starts the IDE anyways. - Forcing to Eclipse Luna 4.4 M6:
I don't mind testing new Eclipse Milestone builds on a regular
basis, but I prefer a stable release for productive use.
This can be configured. *I* forced people to use code recommenders with M6 *now* to make sure that Code Recommenders behaves well :-)
-
Even Eclipse Milestone builds have their rough edges from time
to time, at least speaking on my own experiences.
BTW: This can be configured. On startup you can choose between Eclipse 3.8, 4.3, 4.4. -
- Throwing eclipse installation, workspace and Git repository
to the same location on the same hard drive:
I'd like to have them separated, allowing cross-work between
them (e.g. for Livedoc incubators development, I usually have
both Git Repos (Livedoc and Recommenders Core) imported in my
workspace. )
This is mostly a matter of how I specified the config. I’ll discuss with Eike how I can create a more suitable config for „power users“.
I’ll try to summarize the setup you like :
Git repos, eclipse installation, and workspace usually live under a separate folders, right? So if you could specify them separately you’d be happy? I’m thinking of variables ${local.gitroot}, ${local.wsroot}, ${local.eclipseroot} which (if not set) default to the current setup but if provided by the user in his personal settings, those are used.
All in all, these aren't critical reasons against an usage of
Oomph imo, but it didn't saved me any time or configuration
effort, due to the reasons above.
So the advantages doesn't take over (at least for me :) ).
I didn't take the time and make an Oomph setup for Livedoc, but
from my users point of view, Yoxos does basically the same. (Not
that I am a fan of Yoxos) However, there are clearly benefits for eclipse beginners, as
there are no needs of eclipse configuration, plugin installing
etc.
At least for Recommenders core development, doesn't fit for
Livedoc Incubator atm, due to the separated Git repo's and the
different target platforms.
Why is this no fit for Livedoc? Git repos and target platforms can be specified for each config. If we create a livedoc config it would get/use it’s own config and target platform.
Thanks for your valuable feedback.
Best, Marcel
Best regards,
Patrick
Am 23.03.2014 16:08, schrieb Marcel
Bruch:
Hi Yasser,
thanks for testing this!
Setup was simplified. You can skip step 2 now - our configuration is no baked into Oomph. Just run the installer and pick Code Recommenders from the menu.
Yasser, this tool (unfortunately) has some implications on the Gsoc scope :-\ To get the most out of your Gsoc we should adjust (or redefine) it. No worries, we’ll take care. Andreas will talk with you about the details on Monday!
Best,
Marcel
Am 23.03.2014 um 15:53 schrieb Yasser Aziza <yasser.aziza@xxxxxxxxxxxxxx>:
Hey Marcel,
I have tested this tool on my Mac (OS X 10.9.2),
all works fine for me.
Very nice Tool!
Cheers,
Yasser.
Am 22.03.14 17:45, schrieb Marcel Bruch:
Hi,
at EclipseCon I learned about Eclipse OOMPH - and IDE and workspace provisioning tool. I created a configuration for Code Recommenders that would allow contributors to easily get the latest Eclipse IDE (Luna M6) with Egit, Xtend, M2E, M2E Extensions, and Marketplace Client already installed.
The workspace created by OOMPH also contains the default workspace settings and Java Code formatting rules and common compiler settings for Code Recommenders.
OOMPH also checks out the Git repository and can potentially import these projects in the workspace. Unfortunately this does not work with code recommender since we don’t check in .project files but get them generated by Maven.
However, since the git repo is already cloned, users only have to import the projects using the M2E Import wizard manually and are almost done.
I’d like to ask a couple of people to test that system. Andreas, Patrick, and Sascha: Could you do me a favor and test this setup?
Steps to do:
1. Download the OOMPH Installer from [1]
2. Place the attached recommenders.setup file into the same folder as the unzipped OOMPH Installer. Note, on Mac that file has to be placed under /Setup.App/Contents/MacOs/. See [2], step 8 for details.
3. Start the installer and pick „Code Recommenders“ from the installer Window:
4. After you clicked on install, OOMPH will download a fair amount of Jars and set up your Eclipse installation under the „Install Folder“ you specified in step 3. Follow the instructions until OOMPH seems to be done.
5. Then you need to manually import the Maven projects:
6. Last, click on the refresh button. This will do a couple of things - most interestingly set the target platform to Kepler:
After that, you should have a ready-to-use workspace and fresh Eclipse installation.
Please let me know if this works for you!
Thanks,
Marcel
[1] https://wiki.eclipse.org/Eclipse_Oomph_Installer
[2] https://wiki.eclipse.org/Eclipse_Oomph_Authoring
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/recommenders-dev
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/recommenders-dev
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/recommenders-dev
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/recommenders-dev
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/recommenders-dev
|
