Importing settings from a windows share

Hello,

When I try to import in IntelliJ 13.1.3 settings from a jar that is located on my local drive, it works perfectly. The file chooser automatically updates the tree when I enter something like E:\bla\bla\.

Unfortunately, when I paste in a path to a remote location (\\myshare\ideConfig\idea\), it doesn't update the tree, nor let me import the jar file when I specify the full path to the file. A drag and drop, like it is hinted at the bottom of the window, doesn't work either.

I am trying to setup an environment so that many developpers will be able to share one base configuration. It's an obvious step to make the settings.jar available on a remote share.

How can I make this work? Is it a bug or a misuse of IDEA?

Thanks for the help :)

Sébastien

4 comments
Comment actions Permalink

Hello.

This is known limitation of current version.
Just for reference, the request about file chooser: http://youtrack.jetbrains.com/issue/IDEABKL-4983
And general request: http://youtrack.jetbrains.com/issue/IDEA-123273

Could you try to map the network path to local drive?

Regards,
Alexander.

0
Comment actions Permalink

Hello,

Thanks for your answer!

I'm guessing that, since these issues were opened 7 and 9 years ago, they will never be fixed?

Or is it useful to add a comment/vote for these issues?

My company is currently starting to use other IDEs than Eclipse, and shared settings are definitely something that I will use to ensure that everybody has a similar configuration. The share will only be used once in a while, so nobody will map it to a local letter only to use it once or twice a year. Having people copy the settings.jar to their local drive before importing is certainly not a big issue, but it gives a bad image of the product.

Sébastien

0
Comment actions Permalink

Comments and votes are useful, since they can change development plans to fix this or that issue. BTW, I have added a link to this discussion there. So, your opinion should not be lost.

Yes, UNC problem is old, but I don't think it means anything. There is no policy to fix only new issues.

As you can see in the issue history: http://youtrack.jetbrains.com/issue/IDEA-123273#tab=History - the developer has picked it from the backlog just this April. He probably has some serious plans.

Regards,
Alexander.

0
Comment actions Permalink

Ok thanks a lot! :)

Sébastien

0

Please sign in to leave a comment.