SSH keys [message #1444694] |
Tue, 14 October 2014 12:21 |
|
Dear Oomph team,
I am newbie to the papyrus community. So I have started with the oomph installer to have a fully compatible developer environment.
Oomph is a great tool that really sipmlify the installation process.
Nevertheless, I have noticed one point that could perhaps be upgraded:
SSH
When configuring the oomph installer, I have initially chosen the ssh git configuration.
Badly, it seems that Eclipse Oomph where not able to get the key that was store in my .ssh folder.
So I had to switch to https configuration and then after installation I have switched back to ssh configuration with manual import of my key (windows>preference>ssh)
>>Perhaps I have missed something ot it could be good to allow to reference specific ssh key in the oomph installer?
Thanks
Francois
|
|
|
Re: SSH keys [message #1444709 is a reply to message #1444694] |
Tue, 14 October 2014 12:49 |
Ed Merks Messages: 33258 Registered: July 2009 |
Senior Member |
|
|
Francois,
Comments below.
On 14/10/2014 2:21 PM, Francois Le Fevre wrote:
> Dear Oomph team,
> I am newbie to the papyrus community. So I have started with the oomph
> installer to have a fully compatible developer environment.
> Oomph is a great tool that really sipmlify the installation process.
>
> Nevertheless, I have noticed one point that could perhaps be upgraded:
>
> SSH
> When configuring the oomph installer, I have initially chosen the ssh
> git configuration.
> Badly, it seems that Eclipse Oomph where not able to get the key that
> was store in my .ssh folder.
It's not Oomph itself that's using it. It's EGit that uses that...
> So I had to switch to https configuration and then after installation
> I have switched back to ssh configuration with manual import of my key
> (windows>preference>ssh)
We need to understand exactly what the problem is here. We use SSH
ourselves all the time without a problem. But perhaps there are things
like not using the standard default locations. In the end, we take
whatever settings you configure in the installer and copy
String[] networkPreferences = new String[] { ".settings",
"org.eclipse.core.net.prefs" };
URI sourceLocation =
SetupContext.CONFIGURATION_LOCATION_URI.appendSegments(networkPreferences);
if (getURIConverter().exists(sourceLocation, null))
{
URI targetURI =
URI.createFileURI(getProductConfigurationLocation().toString()).appendSegments(networkPreferences);
ResourceCopyTask resourceCopyTask =
SetupFactory.eINSTANCE.createResourceCopyTask();
resourceCopyTask.setSourceURL(sourceLocation.toString());
resourceCopyTask.setTargetURL(targetURI.toString());
performTask(resourceCopyTask);
}
So I would generally expect that whatever you've configure in the
installer will look exactly the same when you check again in the
launched freshly installed IDE.
If that's not the case, we need a bugzilla with clear/specific
instructions for how to reproduce the problem.
>
>>> Perhaps I have missed something ot it could be good to allow to
>>> reference specific ssh key in the oomph installer?
>
> Thanks
> Francois
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: SSH keys [message #1446156 is a reply to message #1444709] |
Thu, 16 October 2014 12:48 |
|
Ed,
I have investigated a little by doint several oomph installation.
finnaly, I have found that the initial CEA laptop computer that I got from the IT team to not have a windows HOME environmental property that links to the good home where the .ssh folder is located.
So sorry, oomph ssh configuration is fully operationnal when the home varibale where ssh folder is well setup!
have a good day.
Francois
|
|
|
|
Re: SSH keys [message #1713558 is a reply to message #1713425] |
Thu, 05 November 2015 07:16 |
Ed Merks Messages: 33258 Registered: July 2009 |
Senior Member |
|
|
The Javadoc of System.getProperties suggests that user.home is
guaranteed to be defined, so I assume all plugins use that. In any
case, it's not Oomph that uses .ssh keys, it's EGit/JJit, so best to ask
about this topic on the EGit forum.
On 04/11/2015 4:45 PM, J.R. Heisey wrote:
> By default Windows does not create the HOME environment variable.
> It does create
>
> HOMEDRIVE=C:
> HOMEPATH=\Users\username
>
> I suggest that the plug in use the Windows variables when running on
> Windows.
>
> Regards,
> J.R.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03056 seconds