[ 
https://issues.apache.org/jira/browse/JCRVLT-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCRVLT-575:
----------------------------------
    Description: 
In this case, we currently see:

 

{color:#1d1c1d}org.apache.jackrabbit.vault.packaging.registry.impl.FSPackageRegistry
 bundle org.apache.jackrabbit.vault:3.5.6 
(151)[org.apache.jackrabbit.vault.packaging.registry.impl.FSPackageRegistry(264)]
 : The activate method has thrown an exception 
(java.nio.file.FileAlreadyExistsException: /path/to/file){color}

 

{color:#1d1c1d} {color}

  was:
In this case, we currently see:

 

{color:#1d1c1d}org.apache.jackrabbit.vault.packaging.registry.impl.FSPackageRegistry
 bundle org.apache.jackrabbit.vault:3.5.6 
(151)[org.apache.jackrabbit.vault.packaging.registry.impl.FSPackageRegistry(264)]
 : The activate method has thrown an exception 
(java.nio.file.FileAlreadyExistsException: /path/to/file){color}

 

{color:#1d1c1d}Would be nice if it pointed out that there's a symlink where a 
directory is supposed to be present or created. Or better yet, modify the code 
to follow the symlink.
{color}


> do not fail if home path for package registry contains a symlink
> ----------------------------------------------------------------
>
>                 Key: JCRVLT-575
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-575
>             Project: Jackrabbit FileVault
>          Issue Type: Task
>          Components: Misc
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 3.5.8
>
>
> In this case, we currently see:
>  
> {color:#1d1c1d}org.apache.jackrabbit.vault.packaging.registry.impl.FSPackageRegistry
>  bundle org.apache.jackrabbit.vault:3.5.6 
> (151)[org.apache.jackrabbit.vault.packaging.registry.impl.FSPackageRegistry(264)]
>  : The activate method has thrown an exception 
> (java.nio.file.FileAlreadyExistsException: /path/to/file){color}
>  
> {color:#1d1c1d} {color}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to