[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-5507) Cannot update SVN trunk under Windows, too long file paths

Viacheslav Kabanovich (JIRA) jira-events at lists.jboss.org
Thu Dec 17 10:18:31 EST 2009


     [ https://jira.jboss.org/jira/browse/JBIDE-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viacheslav Kabanovich resolved JBIDE-5507.
------------------------------------------

    Resolution: Done


> Cannot update SVN trunk under Windows, too long file paths
> ----------------------------------------------------------
>
>                 Key: JBIDE-5507
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5507
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi (jsr-299)
>    Affects Versions: 3.1.0.GA
>         Environment: Windows XP SP3; Windows Vista SP2
>            Reporter: Yahor Radtsevich
>            Assignee: Viacheslav Kabanovich
>            Priority: Blocker
>             Fix For: 3.1.0.GA
>
>
> There are paths more than 350 symbols in the /trunk/cdi/tests/ , while Windows supports only 255. The trunk cannot be updated on the machines running Windows.
> 'svn update' exits with the following error:
> ------
> svn: Can't create directory 'cdi\tests\org.jboss.tools.cdi.core.test\resources\tck\extensions\ContainerEventBrokenProces
> sBeanObserverRegistersException\JavaSource\org\jboss\jsr299\tck\tests\extensions\container\event\broken\processBeanObser
> verRegistersException': The filename or extension is too long.
> ------
> The longest file path in the trunk (368 symbols): https://svn.jboss.org/repos/jbosstools/trunk/cdi/tests/org.jboss.tools.cdi.core.test/resources/tck/context/PassivatingBrokenDependentScopedProducerMethodReturnsNonSerializableObjectForInjectionIntoStatefulSessionBean/JavaSource/org/jboss/jsr299/tck/tests/context/passivating/broken/dependentScopedProducerMethodReturnsNonSerializableObjectForInjectionIntoStatefulSessionBean/MaarianHaminaLocal_Broken.java

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list