Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Why not just allow the 2 possibilities.</p> <p>I'm OK for the case of a big project which generate many files in the .metadata folder. Even if it's pretty simple to put the .metadata line in the .gitignore in order to inprove performances.</p> <p>But in my case (Android development), I have about 35 differents projects containing only 50 files.</p> <p>All this projects are in different worspaces containing the application project and the libraries projects for this app. (One repository with submodules per application)</p> <ul> <li><p>Must I only have one workspace with all my projects inside (spending time to scroll/close/open projects in the package explorer) ?</p></li> <li><p>Must I manage 2 different base folders (Projects and Worskspaces) with the last one containing just the .metadatas folders of all my projects ?</p></li> </ul> <p>For me this doesn't have sense.</p> <p>Message to the EGit team :</p> <p>Why changing the way developers usually organize their projects folders :</p> <p>---- Worspace</p> <p>---- Worspace / .metada</p> <p>-----Worspace / .git</p> <p>-----Worspace / Project1</p> <p>-----Worspace / LibraryProject1</p> <p>-----Worspace / LibraryProject2</p> <p>I understand the performance reason but for just 5% of developers with very big projects (generating big .metadata) you just not allow us to structure our projects like Eclipse tells us to do since years.</p> <p>Could you just, even if a message warns us that's it's not recommended, don't block the clone process to the worspace folder ("C:\Worspaces\ is not an empty directory")</p> <p>EGit is a great tool but I'm really thinking of using the Bash way beacause of this<br> limitation.</p> <p>Thanks for your reply</p> <p>PS : There are many different cases of developement under Eclipse. If it's just a performance issue and if it doesn't make EGit crash, please just warn us about it but don't block us in case of small projects.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload