[ https://issues.jboss.org/browse/JBIDE-13112?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13112: --------------------------------------------- how about cloning into c:\ws\jbt-trunk instead ? Crazy thought but would that be enough ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13112?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13112: --------------------------------------------- btw. which version of Windows is this ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13112?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-13112 at 11/20/12 8:32 AM: --------------------------------------------------------------- Yes shortening path for jenkins jobs workspace works. It will work unless longer path is added to git repo(s). It's not nice for users which wanna clone our repo to directory with longer absolute path to get this error. I think length of path to source file/directory within our repos should be resonable what i think is not case for string "dependentScopedProducerFieldReturnsNonSerializableObjectForInjectionIntoStatefulSessionBean" used as name for subdirectory. It's 92 characters long. And what is worse it's not clear immediately when git clone command fails that reason is long absolute path. Error message from git clone command it's not saying it clearly and user needs some time to find out what went wrong. Probably developers and QE would have to take care to use paths short enought. I don't know about any way how to ensure this using some tools. It happened on MS Windows 7 64 bit. was (Author: vpakan): Yes shortening path for jenkins jobs workspace works. It will work unless longer path is added to git repo(s). It's not nice for users which wanna clone our repo to directory with longer absolute path to get this error. I think length of path to source file/directory within our repos should be resonable what i think is not case for string "dependentScopedProducerFieldReturnsNonSerializableObjectForInjectionIntoStatefulSessionBean" used as name for subdirectory. It's 92 characters long. And what is worse it's not clear immediately when git clone command fails that reason is long absolute path. Error message from git clone command it's not saying it clearly and user needs some time to find out what went wrong. Probably developers and QE would have to take care to use paths short enought. I don't know about any way how to ensure this using some tools. It happened on MS Windows XP 64 bit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13112?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-13112: ------------------------------------- I don't know if it's possible to tell to git to use long UNC names when extracting files/directories -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13112?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13112: ---------------------------------------- Fix Version/s: 4.1.x Priority: Critical (was: Major) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13112?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13112: ----------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.1.x) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-13112?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13112: ---------------------------------------- Yes, these file names came from the CDI TCK project. But I believe it's not a big problem to rename the longest ones. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira