Difference in importing a project in eclipse against cloning it through git and then opening it in eclipse





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I am working on a git maven project.
We are a team of 6 developers.
I use git bash and tortoise git inorder to clone the project branch, whereas the rest of my team directly uses the git plugin in eclipse and import it from the git URL.
I came across a difference in these both processes that the project name in my eclipse was different than what happened to be with the rest of my teams'.
Am i missing something here?
Am i following a bad practise?
Why is there a difference in the project names when both my team and me are importing the same project?










share|improve this question


















  • 1





    Do the shared Git repositories contain the .project files (in which Eclipse stores the project name)?

    – howlger
    Nov 25 '18 at 8:04











  • Well I don't know that right now.. I will go check that tomorrow and report back. I think this has to do something with the project names being different. Thankyou very much.

    – Akshay Joshi
    Nov 25 '18 at 10:01




















1















I am working on a git maven project.
We are a team of 6 developers.
I use git bash and tortoise git inorder to clone the project branch, whereas the rest of my team directly uses the git plugin in eclipse and import it from the git URL.
I came across a difference in these both processes that the project name in my eclipse was different than what happened to be with the rest of my teams'.
Am i missing something here?
Am i following a bad practise?
Why is there a difference in the project names when both my team and me are importing the same project?










share|improve this question


















  • 1





    Do the shared Git repositories contain the .project files (in which Eclipse stores the project name)?

    – howlger
    Nov 25 '18 at 8:04











  • Well I don't know that right now.. I will go check that tomorrow and report back. I think this has to do something with the project names being different. Thankyou very much.

    – Akshay Joshi
    Nov 25 '18 at 10:01
















1












1








1








I am working on a git maven project.
We are a team of 6 developers.
I use git bash and tortoise git inorder to clone the project branch, whereas the rest of my team directly uses the git plugin in eclipse and import it from the git URL.
I came across a difference in these both processes that the project name in my eclipse was different than what happened to be with the rest of my teams'.
Am i missing something here?
Am i following a bad practise?
Why is there a difference in the project names when both my team and me are importing the same project?










share|improve this question














I am working on a git maven project.
We are a team of 6 developers.
I use git bash and tortoise git inorder to clone the project branch, whereas the rest of my team directly uses the git plugin in eclipse and import it from the git URL.
I came across a difference in these both processes that the project name in my eclipse was different than what happened to be with the rest of my teams'.
Am i missing something here?
Am i following a bad practise?
Why is there a difference in the project names when both my team and me are importing the same project?







eclipse git github eclipse-plugin






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 25 '18 at 5:16









Akshay JoshiAkshay Joshi

82




82








  • 1





    Do the shared Git repositories contain the .project files (in which Eclipse stores the project name)?

    – howlger
    Nov 25 '18 at 8:04











  • Well I don't know that right now.. I will go check that tomorrow and report back. I think this has to do something with the project names being different. Thankyou very much.

    – Akshay Joshi
    Nov 25 '18 at 10:01
















  • 1





    Do the shared Git repositories contain the .project files (in which Eclipse stores the project name)?

    – howlger
    Nov 25 '18 at 8:04











  • Well I don't know that right now.. I will go check that tomorrow and report back. I think this has to do something with the project names being different. Thankyou very much.

    – Akshay Joshi
    Nov 25 '18 at 10:01










1




1





Do the shared Git repositories contain the .project files (in which Eclipse stores the project name)?

– howlger
Nov 25 '18 at 8:04





Do the shared Git repositories contain the .project files (in which Eclipse stores the project name)?

– howlger
Nov 25 '18 at 8:04













Well I don't know that right now.. I will go check that tomorrow and report back. I think this has to do something with the project names being different. Thankyou very much.

– Akshay Joshi
Nov 25 '18 at 10:01







Well I don't know that right now.. I will go check that tomorrow and report back. I think this has to do something with the project names being different. Thankyou very much.

– Akshay Joshi
Nov 25 '18 at 10:01














1 Answer
1






active

oldest

votes


















1















Am I following a bad practice?




No, you're not following a bad practice. It is merely a matter of preference. The project name in each developer's local environment makes no difference, as long as each developer can identify the active project.




Why is there a difference in the project names when both my team and I are importing the same project?




It's hard to say given the context of the question. Some things could have happened that made the project names different.




  1. You cloned the repository in a directory with a different name than the remote repository.

  2. You used the default values in the wizard when importing the project into Eclipse. The default Eclipse workspace is not where you cloned it, but is local to the Eclipse installation.

  3. The Eclipse Git plugin names the project something other than what the remote name is.


If you are concerned about this (which you shouldn't be), then the standard practice to follow is to have the cloned directory root to be the same name as the remote.






share|improve this answer
























  • Thankyou very much @Mania36 for clearing my doubts. I think am quite confident now.

    – Akshay Joshi
    Nov 25 '18 at 10:05












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53464862%2fdifference-in-importing-a-project-in-eclipse-against-cloning-it-through-git-and%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1















Am I following a bad practice?




No, you're not following a bad practice. It is merely a matter of preference. The project name in each developer's local environment makes no difference, as long as each developer can identify the active project.




Why is there a difference in the project names when both my team and I are importing the same project?




It's hard to say given the context of the question. Some things could have happened that made the project names different.




  1. You cloned the repository in a directory with a different name than the remote repository.

  2. You used the default values in the wizard when importing the project into Eclipse. The default Eclipse workspace is not where you cloned it, but is local to the Eclipse installation.

  3. The Eclipse Git plugin names the project something other than what the remote name is.


If you are concerned about this (which you shouldn't be), then the standard practice to follow is to have the cloned directory root to be the same name as the remote.






share|improve this answer
























  • Thankyou very much @Mania36 for clearing my doubts. I think am quite confident now.

    – Akshay Joshi
    Nov 25 '18 at 10:05
















1















Am I following a bad practice?




No, you're not following a bad practice. It is merely a matter of preference. The project name in each developer's local environment makes no difference, as long as each developer can identify the active project.




Why is there a difference in the project names when both my team and I are importing the same project?




It's hard to say given the context of the question. Some things could have happened that made the project names different.




  1. You cloned the repository in a directory with a different name than the remote repository.

  2. You used the default values in the wizard when importing the project into Eclipse. The default Eclipse workspace is not where you cloned it, but is local to the Eclipse installation.

  3. The Eclipse Git plugin names the project something other than what the remote name is.


If you are concerned about this (which you shouldn't be), then the standard practice to follow is to have the cloned directory root to be the same name as the remote.






share|improve this answer
























  • Thankyou very much @Mania36 for clearing my doubts. I think am quite confident now.

    – Akshay Joshi
    Nov 25 '18 at 10:05














1












1








1








Am I following a bad practice?




No, you're not following a bad practice. It is merely a matter of preference. The project name in each developer's local environment makes no difference, as long as each developer can identify the active project.




Why is there a difference in the project names when both my team and I are importing the same project?




It's hard to say given the context of the question. Some things could have happened that made the project names different.




  1. You cloned the repository in a directory with a different name than the remote repository.

  2. You used the default values in the wizard when importing the project into Eclipse. The default Eclipse workspace is not where you cloned it, but is local to the Eclipse installation.

  3. The Eclipse Git plugin names the project something other than what the remote name is.


If you are concerned about this (which you shouldn't be), then the standard practice to follow is to have the cloned directory root to be the same name as the remote.






share|improve this answer














Am I following a bad practice?




No, you're not following a bad practice. It is merely a matter of preference. The project name in each developer's local environment makes no difference, as long as each developer can identify the active project.




Why is there a difference in the project names when both my team and I are importing the same project?




It's hard to say given the context of the question. Some things could have happened that made the project names different.




  1. You cloned the repository in a directory with a different name than the remote repository.

  2. You used the default values in the wizard when importing the project into Eclipse. The default Eclipse workspace is not where you cloned it, but is local to the Eclipse installation.

  3. The Eclipse Git plugin names the project something other than what the remote name is.


If you are concerned about this (which you shouldn't be), then the standard practice to follow is to have the cloned directory root to be the same name as the remote.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 25 '18 at 5:28









Mania36Mania36

284




284













  • Thankyou very much @Mania36 for clearing my doubts. I think am quite confident now.

    – Akshay Joshi
    Nov 25 '18 at 10:05



















  • Thankyou very much @Mania36 for clearing my doubts. I think am quite confident now.

    – Akshay Joshi
    Nov 25 '18 at 10:05

















Thankyou very much @Mania36 for clearing my doubts. I think am quite confident now.

– Akshay Joshi
Nov 25 '18 at 10:05





Thankyou very much @Mania36 for clearing my doubts. I think am quite confident now.

– Akshay Joshi
Nov 25 '18 at 10:05




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53464862%2fdifference-in-importing-a-project-in-eclipse-against-cloning-it-through-git-and%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







這個網誌中的熱門文章

Tangent Lines Diagram Along Smooth Curve

Yusuf al-Mu'taman ibn Hud

Zucchini