uschindler commented on pull request #631:
URL: https://github.com/apache/solr/pull/631#issuecomment-1039190301


   > These are supposed to be fine on Windows, though.
   
   Unfortunately no, to use symlinks in Windows 10, you need multiple stuff and 
it is not working out of box:
   - You need to enable Windows 10 developer mode. If you do this, also users 
are allowed to create symlinks, otherwise you need admin privileges. On the 
Jnekins server this is by default the case, this is why it works there.
   - When checking out the repository you have to pass command line parameters 
to "enable symlinks". Usual tools like TortoiseGit (I use that, does not do 
this). A global config property does not work, as GIT requires the property to 
be passed always when checking out. Once you have the checkout it works. But if 
you have no developer mode or admin access (and klick on the UAC prompt) it 
breaks again. So this is a pain! Microsoft misdesigned symlinks, because they 
were afraid of bad things done with them (like you place a symlink there 
pointing to temp directory with some häckidihickhack malware and nowbody would 
notice). So without developer mode and some extra settings and also extra 
command line options (because Git people did not want the git client to be 
forcefully executed with admin rights, so you need to opt-in) your hopeless.
   
   My proposal would be to have:
   - a simple list of files in the example directories
   - possibly a a "gitignore *.java" file in each
   - a Gradle build step that reads the file and copies the files over to the 
examples directory. The good thing with that: symlinks get quickly out of sync 
because nothing checks that they are still valid. The gradle task would fail if 
the example file was moved away and symlink not updated.
   
   Ideally the copied files would be below some build/examplefiles folder (if 
thats pssible the gitignore would not be needed)!
   
   Uwe
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to