Android Marketplace 更新 &日食项目
因此，我设法在市场上推出了几个应用程序，只是偶然想到在 Eclipse 中管理我的项目/应用程序以适应市场未来更新的最佳方式是什么。我的问题在于 Eclipse 以及应用更新时如何处理我的项目/应用程序。
我是否只需复制我的项目/应用程序，粘贴它并相应地增加版本信息？或者我是否持续致力于我已发布的项目/应用程序？或者...是否有推荐/首选的方法来解决这个问题。由于它们在市场上表现良好，我很担心做一些会给我以后带来问题的事情。
并且不要更改包名称....对吗？
这是我目前在市场上拥有的...
首先，每个人的帖子都非常有帮助，我花了一些时间通过提供的链接查看文档。
所以……当我这么说时，请做好迎接冲击的准备。作为一个从未在我的项目中使用过任何形式的 SCM 的人，这对我来说是全新的（因为每个人的脸都在畏缩），这就是为什么我首先要问最初的问题。我讨厌在不做研究的情况下告诉我任何事情......所以在过去的几个小时内，在 eclipse 中使用 git 我看到了以下内容：
团队>共享项目...忽略...任何标签（用于版本信息）这就是我所追求的...提交...然后
克隆？文件->导入-> git->此时，一旦我克隆了我的项目，Git 存储库是否会使用新版本信息创建一个新标签，并再次执行提交过程？如果是这种情况，我的 Git 存储库中现在有两个项目。其中一个具有单个标签 1.0，另一个项目包含两个标签 1.0 和 1.1，当我查看历史记录时，我看到两个标签版本 1.0 和版本 1.1。然后我只需从存储库中切换我需要的资源？
我只是想在开始在已经相当广泛的现有项目上实施其中一些之前确保我的流程是正确的。至于其余的，我只是要即时学习......分支
So I have managed to get a couple apps up on the marketplace only to have a stray thought of what is the best way to go about managing my projects/apps within eclipse to accommodate future updates to the marketplace. My question resides within Eclipse and what to do with my projects/apps as I apply updates.
Do I simply copy my project/app, paste it and the increment the version information accordingly? Or am I continuously working on my published project/app? Or...Is there a recommended/preferred method of going about this. Since they are up and good on the marketplace I am leery of doing something that will cause problems for me later on down the line.
And don't change the package name....correct?
This is what I currently have on the Marketplace...
First of all, everyone's posts were very helpful and I have spent some time looking over documentation through the links provided.
So...and brace for impact as I say this. Being one who has NEVER used any form of SCM for my projects this is all new to me (as everyone's faces cringe), which is why I am asking the original question in the first place. I hate to say tell me anything without doing my research...so within the past few hours using git within eclipse I have gleamed the following:
Team > Share Project ...ignores...any tags(for version info)which is what I am after...commits...THEN
Clone? File -> Import -> Git -> Git Repository at this point once I have cloned my project do I create a new tag with the new version info, and go through the commit process again? If this is the case I now have two items in my Git Repository. One of which has the single tag of 1.0, and the other item which contains two tags 1.0 and 1.1, and when I look at the history I see two tags Version 1.0 and Version 1.1. Then I just switch between the resources I need from within the repository?
I just want to make sure my process is correct before I begin to implement some of this on existing projects that are pretty extensive already. As for the rest I am just going to learn on the fly...branches
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您可能想要使用 SVN 或 git 等版本控制系统或数十种其他选项之一，并持续更新 Eclipse 中的单个项目。使用源代码控制的好处是，您可以分支到新项目中进行重大更改，更新现有代码以进行较小的更改，并标记分支，以便将来可以恢复到旧快照。
我个人使用 bitbucket，它是远程托管的并且是免费的。它支持 SVN 和 Mercurial。
You might want to use a revision control system like SVN or git or one of dozens of other options, and continuously update the single project in Eclipse. The benefit of using source control is that you can branch into a new project for major changes, update your existing code for minor changes, and tag the branches so you can revert back to an old snapshot in the future.
I personally use bitbucket which is hosted remotely and is free. It supports SVN and Mercurial.
不，不要更改包名称，这将使其成为新应用程序，而不是升级原始应用程序。
使用版本控制系统，例如 SVN。
管理代码完整工作状态的标签（通过 svn），以便您随时可以恢复到该标签。
当准备好新版本时，增加版本号。等并在市场上更新...
编辑添加有问题后：
不要对各种 GIT/SVN 工作感到困惑。主要目的是它们将允许您将代码来回切换到过去的任何点，这允许您以正确的方式进行编码，知道您始终可以恢复到工作状态.. 当多个人在相同的代码库和可能相同的文件上工作时，这在团队中绝对有更多的好处...
No, dont change the package name, that will make it new app, instead of upgrade of original.
Use a version control system, like SVN.
Manage Tags for a complete working state of code(through svn), so you can always revert back to that tag.
When ready for new release, increment version no. etc and update on market...
EDIT After addition in question:
Don't get much confused with various GIT/SVN working.. There main purpose is that they will allow you to switch your code back and forth to any point in past, that allows you to code in a way properly knowing that you can always revert back to a Working state.. and it is definitely of much more benefit in a Team , when multiple people are working on same codebase and possibly same files...
作为 SVN 的长期用户，我推荐 subclipse (svn for eclipse)。当您准备好发布应用程序的另一个版本时，为发布版本创建一个“标签”，您将始终能够返回到该确切版本。
SVN 有优秀的文档。还有 TortoiseSVN 用于 Eclipse 之外的存储库工作。
Being a long-time user of SVN, I recommend subclipse (svn for eclipse). When you're ready to release another version of your app, create a 'tag' for the release version and you'll always be able to go back to that exact version.
SVN has excellent docs. There is also TortoiseSVN for repo work outside of eclipse.