Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: Aptana Studio 3.0 (Final)
-
Component/s: None
-
Labels:None
Description
{html}<div><p>When importing existing projects from git repositories, the
imported project are automatically shared using aptana studio git
plugin. Users that want to use eGit instead need to disconnect each
imported project and share each one of them using eGit.<br>
A preference should be provided to control such automatic sharing
of imported projects.<br>
Since the eGit plugin is becoming more mature and feature complete
I think it makes more sense for Aptana to extend eGit rather than
replace or even conflict with it (see <a href=
"https://aptanastudio.tenderapp.com/discussions/problems/1988-aptana-git-plugin-disable)">
https://aptanastudio.tenderapp.com/discussions/problems/1988-aptana...</a>.</p></div>{html}
imported project are automatically shared using aptana studio git
plugin. Users that want to use eGit instead need to disconnect each
imported project and share each one of them using eGit.<br>
A preference should be provided to control such automatic sharing
of imported projects.<br>
Since the eGit plugin is becoming more mature and feature complete
I think it makes more sense for Aptana to extend eGit rather than
replace or even conflict with it (see <a href=
"https://aptanastudio.tenderapp.com/discussions/problems/1988-aptana-git-plugin-disable)">
https://aptanastudio.tenderapp.com/discussions/problems/1988-aptana...</a>.</p></div>{html}
Activity
{html}<div><p>We have n option to disable checking for changes remotely, which
we use to poll remotes to update the push/pull indicator in the App
Explorer (if it's being used). I'll add a pref to disable automatic
sharing. Beyond that, what are you seeing in terms of git activity
that causes perf issues? Other than that we don't fire off any git
activity unless there's been some git-related user action, or
Eclipse asks for updates to the dirty status/branch labels for
resources.</p></div>{html}
we use to poll remotes to update the push/pull indicator in the App
Explorer (if it's being used). I'll add a pref to disable automatic
sharing. Beyond that, what are you seeing in terms of git activity
that causes perf issues? Other than that we don't fire off any git
activity unless there's been some git-related user action, or
Eclipse asks for updates to the dirty status/branch labels for
resources.</p></div>{html}
Show
Chris Williams
added a comment - {html}<div><p>We have n option to disable checking for changes remotely, which
we use to poll remotes to update the push/pull indicator in the App
Explorer (if it's being used). I'll add a pref to disable automatic
sharing. Beyond that, what are you seeing in terms of git activity
that causes perf issues? Other than that we don't fire off any git
activity unless there's been some git-related user action, or
Eclipse asks for updates to the dirty status/branch labels for
resources.</p></div>{html}
{html}<div><p>Disabling the "Calculate pull indicator" option was enough in my
case. As default behavior I would suggest not to automatically
share a project with aptana git plugin, so this new option should
be an opt-in and not an opt-out like "Calculate pull indicator".
The reason is that some git project can make git commands very
slow, and with both options as opt-out you can directly lead a
workspace to a grind once such project is imported.</p></div>{html}
case. As default behavior I would suggest not to automatically
share a project with aptana git plugin, so this new option should
be an opt-in and not an opt-out like "Calculate pull indicator".
The reason is that some git project can make git commands very
slow, and with both options as opt-out you can directly lead a
workspace to a grind once such project is imported.</p></div>{html}
Show
fmjrey
added a comment - {html}<div><p>Disabling the "Calculate pull indicator" option was enough in my
case. As default behavior I would suggest not to automatically
share a project with aptana git plugin, so this new option should
be an opt-in and not an opt-out like "Calculate pull indicator".
The reason is that some git project can make git commands very
slow, and with both options as opt-out you can directly lead a
workspace to a grind once such project is imported.</p></div>{html}
{html}<div><p>A pref has been added on our development branch, schedule for
our 3.0 final release. The default is turned on to maintain
existing behavior. Users who want to use egit or just don't like
this behavior can turn it off so that we don't auto0attach our git
support to the project.</p></div>{html}
our 3.0 final release. The default is turned on to maintain
existing behavior. Users who want to use egit or just don't like
this behavior can turn it off so that we don't auto0attach our git
support to the project.</p></div>{html}
Show
Chris Williams
added a comment - {html}<div><p>A pref has been added on our development branch, schedule for
our 3.0 final release. The default is turned on to maintain
existing behavior. Users who want to use egit or just don't like
this behavior can turn it off so that we don't auto0attach our git
support to the project.</p></div>{html}
This way of actually automatically sharing a git project using your
own git plugin is getting in the way of people who do not want to
use git from eclipse or want to use egit instead.<br>
Also there's a performance issue on large git repositories and you
cannot just by default regularly call git to update your views, see
this discussion there:<br>
<a href=
"https://aptanastudio.tenderapp.com/discussions/problems/2471-my-system-becomes-very-slow-when-running-aptana-studio-3">
https://aptanastudio.tenderapp.com/discussions/problems/2471-my-sys...</a></p></div>{html}