On 05/16/2013 01:11 PM, Sergiu Dumitriu wrote: > On 05/16/2013 12:36 PM, Frédéric Bouquet wrote: >> Hi, >> >> I'm not (yet ;)) a XWiki developper but concerning this issue with windows, >> I'd like to propose an other way of adressing it. >> >> Several developpers in my company work on windows + eclipse and encounter >> the same issue with bonita engine. They found a solution by closing all >> projects they don't work on, using the corresponding packages from a maven >> repository. It seems a bit painful at the beginning but with good >> practices, it's ok (by the way, working with eclipse with all projects open >> should not be simple). As far as I remember, when I was working on windows >> and idea, I never had the issue. Do you know if the issue is only with >> eclipse or append also when using maven in command line or using an other >> IDE ? >> >> Back to the main idea, instead of doing this huge refactoring which will >> impact all XWIki developpers, the alternative may be for one guy to try >> developping on windows with different IDEs and then provide a way of >> working on each environment. The cost of such work may be a few hours to >> find a solution and write some guidelines/good practices. The result for >> new developpers would be more or less as learning new coding rules. >> >> WDYT ? >> > > The problem isn't IDE-related at all, it's about the filesystem. Windows > doesn't allow creating files with a path longer than 255 characters, so > it will fail at attempting to fetch the sources from GitHub. > > And that's not actually true, the filesystem itself does allow long path > names, it's the Windows API that is broken. There are alternative APIs > that allow longer path names (32k chars), but it seems that very few > developers use those instead of the default ones (not even the official > Windows applications seem to use those), so most applications are broken. > > This is why using cygwin works, because it correctly uses the modern > APIs. And maybe in time other tools will work as well, but we can't say > that "your tool is broken, use something else" when the tool works for > 99.9% of all the other software packages. > > http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath >
A good quote from http://www.codinghorror.com/blog/2006/11/filesystem-paths-how-long-is-too-long.html I think 260 characters of path is more than enough rope to hang ourselves with. If you're running into path length limitations, the real problem isn't the operating system, or even the computers. The problem is the deep, dark pit of hierarchies the human beings have dug themselves into. -- Sergiu Dumitriu http://purl.org/net/sergiu _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
