[ 
https://jira.nuxeo.com/browse/NXP-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien Carsique updated NXP-8659:
---------------------------------

    Description: 
Path length is too long for Windows, causing issues like:
<< [exec] error: unable to create file 
nuxeo-platform-directory/nuxeo-platform-directory-core/src/test/java/org/nuxeo/ecm/directory/localconfiguration/DirectoryLocalConfigurationRepositoryInit.java
 (No such file or directory) >>

Even under "powerful" OS where path length is not an issue, having so long 
paths and duplication in names is a pain.

There are a few constraints:
 * it's better (even required) for an artifact to live in a directory with the 
same name.
 * it's useful to have parent directories of SCM repositories starting with the 
prefix "nuxeo-".

Possible improvements:
 * remove the prefix "nuxeo-" from most modules (the group is enough to know 
they are Nuxeo modules)
 * remove the historical and now useless prefix "nuxeo-platform-" from modules
 * don't repeat the path or group in the module name (for instance: 
"nuxeo-features-test" living in "nuxeo-features" could be simply named "test")
 * reduce filenames length for the longer ones
 * setup rules on file naming
 * ...

  was:
Path length is too long for Windows, causing issues like:
<< [exec] error: unable to create file 
nuxeo-platform-directory/nuxeo-platform-directory-core/src/test/java/org/nuxeo/ecm/directory/localconfiguration/DirectoryLocalConfigurationRepositoryInit.java
 (No such file or directory) >>

Even under "powerful" OS where path length is not an issue, having so long 
paths and duplication in names is a pain.

There are a few constraints:
 * it's better (even required) for an artifact to live in a directory with the 
same name.
 * it's useful to have parent directories of SCM repositories starting with the 
prefix "nuxeo-".

Possible improvements:
 * remove the prefix "nuxeo-" from most modules (the group is enough to know 
they are Nuxeo modules)
 * remove the historical and now useless prefix "nuxeo-platform-" from modules
 * don't repeat the path or group in the module name (for instance: 
"nuxeo-features-test" living in "nuxeo-features" could be simply named "test")
 * reduce filenames length for the longer ones
 * 


> Reduce source code path length
> ------------------------------
>
>                 Key: NXP-8659
>                 URL: https://jira.nuxeo.com/browse/NXP-8659
>             Project: Nuxeo Enterprise Platform
>          Issue Type: Task
>          Components: Infrastructure
>            Reporter: Julien Carsique
>            Assignee: Julien Carsique
>            Priority: Major
>             Fix For: 6.0
>
>
> Path length is too long for Windows, causing issues like:
> << [exec] error: unable to create file 
> nuxeo-platform-directory/nuxeo-platform-directory-core/src/test/java/org/nuxeo/ecm/directory/localconfiguration/DirectoryLocalConfigurationRepositoryInit.java
>  (No such file or directory) >>
> Even under "powerful" OS where path length is not an issue, having so long 
> paths and duplication in names is a pain.
> There are a few constraints:
>  * it's better (even required) for an artifact to live in a directory with 
> the same name.
>  * it's useful to have parent directories of SCM repositories starting with 
> the prefix "nuxeo-".
> Possible improvements:
>  * remove the prefix "nuxeo-" from most modules (the group is enough to know 
> they are Nuxeo modules)
>  * remove the historical and now useless prefix "nuxeo-platform-" from modules
>  * don't repeat the path or group in the module name (for instance: 
> "nuxeo-features-test" living in "nuxeo-features" could be simply named "test")
>  * reduce filenames length for the longer ones
>  * setup rules on file naming
>  * ...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to